Difference between revisions of "User talk:Kynikos"

From ArchWiki
Jump to navigation Jump to search
(No upstream documentation: ooops.: new section)
(Invalid/undocumented template but it is working: re)
Line 267: Line 267:
  $ /usr/bin/kgtk-wrapper gimp
  $ /usr/bin/kgtk-wrapper gimp
Why is the result the same? Which one have I to choose?
Why is the result the same? Which one have I to choose?
:Hi Wget, those are two different ways to achieve the same HTML result on the page (i.e. enclosing the content in <pre> tags); both are mentioned in [[Help:Style#Code formatting templates]], the first one is documented in [[Template:bc]] and the second one is documented in [[Help:Editing#Code] and [[Help:Cheatsheet]]; you can choose the one you prefer, usually using a space is better for single lines of code, while using bc is better for multiple lines. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 02:58, 25 August 2013 (UTC)
== No upstream documentation: ooops. ==
== No upstream documentation: ooops. ==
Sorry about that Kynikos. Is there documentation on that? I was trying to search for something regarding manpage policy but I failed to find anything. Thanks, [[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 20:33, 24 August 2013 (UTC)
Sorry about that Kynikos. Is there documentation on that? I was trying to search for something regarding manpage policy but I failed to find anything. Thanks, [[User:AdamT|AdamT]] ([[User_talk:AdamT|Talk]]) 20:33, 24 August 2013 (UTC)

Revision as of 02:58, 25 August 2013

Feel free to leave here your comments on my edits or anything else you want to talk about: I'll reply as soon as I can!

Note: Please, add new discussions at the bottom, and with a proper title: I'll take care of removing old discussions once they are exhausted.

Xyne-related page edits after Powerpill, Bauerbill... discontinuation

See Xyne-related page edits after Powerpill, Bauerbill... discontinuation.

Thank you!

Thank you for your massive contribution in initiating -- and completing! -- Help:Style. This is something I have wanted to tackle for years! Well done! -- pointone 14:23, 1 November 2011 (EDT)

In Italian on these occasions we say literally "praised by Caesar" :) I'm proud and eager to be helping the community of this amazing project, and to be working with other enthusiastic people like you! ^^ -- Kynikos 16:02, 1 November 2011 (EDT)


Thanks for fixing the style on the Step By Step Debugging Guide page! --Trontonic 20:52, 6 January 2012 (EST)

Thank you for contributing :) Actually it'd require more fixes, for example the expansion of contractions, see Help:Style for more information.
By the way I've noticed that I put the article in the wrong category: it's somewhat fixed now, but if you're interested, in ArchWiki:Reports#System recovery category we're also talking about the possibility of merging Step By Step Debugging Guide with General Troubleshooting.
-- Kynikos 07:29, 7 January 2012 (EST)

About Template:Filename => Template:ic

Thanks for your contribution and your bot :) But i think the original Template:Filename has its advantage too. Although both template have the same display style now, they actually have different meanings. Filename and codes is different. Now it's very easy to replace filename with ic, but if we want to have a different styles of filename one day, it's rather difficult to find whether it means code or filename. --Skydiver 23:52, 13 February 2012 (EST)

Eheh you're quite late about this :) We discussed it a lot in Help talk:Style and Help talk:Style/Migration to new Code formatting templates (see their history). This is the direction where the wiki is headed, we can't cyclically call into question always the same things, otherwise there will never be any real improvement. Basically we just decided to keep it simple: Template:Filename wasn't used consistently anyway, and there were many cases of ambiguity, so now we're just distinguishing between inline and block code. -- Kynikos 07:29, 14 February 2012 (EST)
Haha~ yeah, i'm late. I didn't notice your notice before and right after i post here I found your bot have done all replacement and Template:Filename has been deleted ... --Skydiver 10:23, 14 February 2012 (EST)
BTW I see you're actually using Wiki Monkey yourself :D Honestly I didn't think somebody was using it except for me, so be advised that if you had installed version 1.6.1 or previous, it won't update automatically to 1.7.x because I've changed the path for configuration files (I won't break the update system anymore, I promise ^^ ). Also please report any bugs you find! -- Kynikos 09:12, 14 February 2012 (EST)
Yep, I found your Wiki Monkey very useful ^_^. I am using 1.7.0 now and find it useful when doing replaces. I'm trying to make a plugin that can automatically find articles w/o i18n template and add i18n template to them, but i've no idea how to do till now.--Skydiver 10:23, 14 February 2012 (EST)
Good to hear that you like it, thanks! I've just released 1.7.2 (just bug fixes), however if you don't enable automatic updates as described in Wiki Monkey#Updates you will have to update manually; unfortunately automatic updates are disabled by default by Scriptish's design, there's nothing I can do about that :)
If you want to fix the header of articles (including the i18n template), simply in editor pages, just write a js function that has the source text and the title as input arguments and the modified source as the return value, and I'll think of Wiki-Monkey-zing it ;)
function fixHeader(title, source) {
    //your code here
    return modSource;
Note that you won't probably be able to just add i18n without also recognizing categories and other stuff that goes at the top of the article.
About doing that on all articles automatically, it's easy to adapt it also for What Links Here pages, since launching the bot from there is already implemented, however you'd more likely need to launch the bot recursively over all the articles under a category and its sub-categories, and that functionality still needs to be implemented. Another way to do that job, which I'd like even more, would be to make Wiki Monkey semi-automatically process the recent changes, suggesting automatic fixes to every article that is edited and letting the user decide whether to apply them or not. A recent changes helper is also in the todo list, but will require some time to develop it.
-- Kynikos 13:14, 14 February 2012 (EST)

Template:Cmd Thanks

Hey Kynikos thanks so much for getting me that template source! I spent many hours working on it and am really happy to have it back. Thank you. --AskApache 11:21, 27 February 2012 (EST)

 :) -- Kynikos 05:49, 28 February 2012 (EST)

html comments in page source

Thank you for constant improvement of articles sources! Most of comments in source code of Common Applications and sub-articles were left by me. These comments were initially added to be later turned into proper categories etc. but due to lack of time I often forget about it. Please consider reorganizing entries instead of just removing comments - it sometimes require a bit of work to determine for example which version of Quake engine is used in every game. --AlexanderR 05:38, 11 March 2012 (EDT)

Html comments are strongly discouraged right because they tend to be forgotten :P
The edits that removed potentially relevant comments are [1] and [2]: the only ways I can think of using those info are either creating subsections (=====PS1=====, =====PS2=====, =====Quake 1=====, ...) or adding those info in the descriptions of the appropriate app entries (I probably prefer the latter solution).
-- Kynikos 07:54, 11 March 2012 (EDT)

Where should translations go?

Hi! I'm wondering where the Archwiki team wants new translations to go? On the page ArchWiki Translation Team I get the feeling that translations should be placed under archlinux.org. At the same time there are national wikis as well, at different stages of development. In my case this is archlinux.se, which only contains a few articles, and is generally lacking links to the main Wiki from what I can see. What is the policy on where to put translations?

Hi and welcome! I'm glad to know that the Swedish website has come back to life :) Since MediaWiki is _not_ designed to handle internationalization (it requires resorting to workarounds like the suffix one we're using here) the ideal goal would be to move each language to its own separate wiki, for ease of maintenance. So, in your case, all Swedish articles should now be moved to wiki.archlinux.se and replaced with interwiki links on at least the English page, e.g. [[sv:Huvudsida]]. -- Kynikos (talk) 15:23, 4 May 2012 (UTC)
Ah, I forgot to mention that if you want to add an interlanguage link to a protected English page, you can just ask on its talk page, and it will be added by one of us admins as soon as possible! -- Kynikos (talk) 15:28, 4 May 2012 (UTC)

On a secondary note - poorly developed regional wikis might work as a black hole for new users (turned off from arch due to lack of documentation) if they do not link to the main wiki for untranslated topics. Ideally they should cover the entire topic tree, and link to the anglish main wiki for untranslated articles. Granted, most potential new users that find a poor regional wiki probably continue searching and eventually find wiki.archlinux.org, but not necessarily all of them.

That's why we must exploit as much as we can the native tool that MediaWiki offers for keeping the various local wikis linked with each other: interlanguage links (example above).
Until the Swedish wiki lacks important articles, at least its Main Page if not also other important articles should instruct Swedish users to search for missing content on the English wiki.
-- Kynikos (talk) 15:23, 4 May 2012 (UTC)


[moved to User talk:Airon90. -- Kynikos (talk) 10:20, 16 December 2012 (UTC)]

Move request

Hey Kynikos,

First of all, I'm sorry to ask this on your talk page. I'm not sure where to ask these kinds of requests and since you're the only mod I know, I'm posting this here. :)

We need help moving GRUB2 to GRUB (motivation: Talk:GRUB2#Move to GRUB), and since the latter already exists, I'm not sure how to do it myself.

Thanks! -- Lonaowna (talk) 20:49, 26 April 2013 (UTC)

Hey Lonaowna, this was indeed a good place to ask, alternatively you could have used ArchWiki talk:Administrators. The article is renamed now, thanks for reporting. -- Kynikos (talk) 04:48, 27 April 2013 (UTC)
Awesome, thanks! :) -- Lonaowna (talk) 07:23, 27 April 2013 (UTC)

About arrows

Hey I'm flu, the one of the latest Libreoffice edits. First I'm sorry for have been a bit impolite :*) .

Here's few questions: if I have to make a list of operations like: menu one -> menu two -> button which arrow should I use? the -> or just > ?

In these cases the quotation '' is the best one?

I've noticed tha many sections header are followed by a blank line, but there is no mention of that in Help:Style. Is there a correct choice?

Flu (talk) 08:57, 18 May 2013 (UTC)

Ciao Flu, I think you're referring to what I wrote on Talk:LibreOffice: you haven't been impolite at all :) Note that if you started writing "reasons" in edit summaries instead of just "what" you've done, you'd become part of I guess the 2% of the wiki users that do it regularly... However that doesn't mean that the 98% of users are impolite ;)
About your questions, as you've noticed we don't have any style rules yet on those topics: you can however start a discussion in Help talk:Style and propose a standardization. About lists of operations, for the moment just take inspiration from another existing article that you like; about blank lines following section headings, just do what you feel is tidier.
-- Kynikos (talk) 17:26, 18 May 2013 (UTC)

Pcmanfm removed packages

I have started a discussion about them: Talk:PCManFM

Replied there, thanks for the heads up. -- Kynikos (talk) 15:25, 11 June 2013 (UTC)

Minor Installation Page Edit

Hi Kynikos,

First of all, I would like to thank you, the wiki maintainers and the contributors for building these docs !

May I suggest an edit to the Installation page. The 2nd point in the 'Download' section currently reads :

  • Install images are signed and it is highly recommend to verify their signature before use. On Arch Linux, this can be done by using
    pacman-key -v <iso-file>.sig

Could this be changed to something like :

  • Install images are signed and it is highly recommend to verify their signature before use. On Arch Linux, this can be done by downloading the .sig file from the download page (or one of the mirrors listed there) to the same directory as your .iso file and then using
    pacman-key -v <iso-file>.sig

I think this might make it a little easier for newcomers. -- Kal

Hi Kal, thank you for reporting this, it's certainly a reasonable request and it's implemented now. However next time you can just simply use the talk page of the protected article you'd like to be modified, in this case it would have been Talk:Installation Guide :) -- Kynikos (talk) 15:42, 21 June 2013 (UTC)

Updating a read-only article

Hey, I noticed that Arch_Packaging_Standards#Directories still lists /usr/sbin, so that needs to be updated per the /usr/bin merger.
-- Jstjohn (talk) 21:15, 23 June 2013 (UTC)

Thanks, it's fixed now :) -- Kynikos (talk) 10:48, 24 June 2013 (UTC)


I'm not speak of english. So, please add [[ru:Help:I18n]] --RemiZOffAlex (talk) 14:41, 12 July 2013 (UTC)

I'm sorry, I don't speak Russian instead, so I can't translate that page: you can try to use http://translate.google.com/ -- Kynikos (talk) 14:46, 12 July 2013 (UTC)
Thanks for the offer, but still possible to create a link to the page, and only leave the translation for the Russian-speaking population of the planet.
--RemiZOffAlex (talk) 14:53, 12 July 2013 (UTC)
Sorry, it's our policy to not include interlanguage links to non-existing articles. Here is the link you want: ru:Help:i18n, you can create the page using http://translate.google.com/ and then some other Russian user will hopefully improve it. -- Kynikos (talk) 15:02, 12 July 2013 (UTC)

Netcfg/Wireless networking/Wireless Setup

[moved to User talk:Ndt#Netcfg/Wireless networking/Wireless Setup, see Help:Discussion#User talk pages. -- Kynikos (talk) 15:37, 16 July 2013 (UTC)]

Quotation marks

Hi, I’m curious to know why you replaced the proper typographic curly quotes “” to typewriter quotes "" in this edit: https://wiki.archlinux.org/index.php?title=Systemd&diff=267151&oldid=267150 Stqn (talk) 16:37, 20 July 2013 (UTC)

Hi, there are several reasons:
Of course if you think you have enough arguments in favour of curly quotes to beat the ones above, please open a discussion in Help talk:Style/Formatting and Punctuation :) -- Kynikos (talk) 04:23, 21 July 2013 (UTC)
Ok, it’s too bad because typewriter quotes look ugly and are harder to read, but I can go with the consistency reason. Note however that the Formatting and punctuation page does not talk about this at all. Thanks for your answer. Stqn (talk) 12:15, 21 July 2013 (UTC)
Thank you for mentioning that, I've added a reminder [3]. -- Kynikos (talk) 12:39, 21 July 2013 (UTC)

Beginners guide / fdisk

Thank you for style fixes. I can't believe i wrote cfdisk instead of cgdisk.

As for the fdisk example section, i don't like the way it looks now.

What i tried to do was just show the exact program output, and superimposed over that the highlighted User input. I don't think it should be split into so many differnt boxes, since what happens is one interactive program session.

It may be better to not show all the programm output, and instead just include usage instructions similar to those given at end of Partitioning article.

I tried to follow style, but the styleguide says to use the Keypress Template for Keypresses. And those i can't use inside the Code templates. So i would have been violating a part of the Style guide anyway.

Well admittetly, maybe i like the previous version just better because i wrote it, hard to say. Will have to think about it some more.

Don't worry, you're doing a good job :) It's just that this case is a bit weird and there's not an easy way of making it look good. Since you're representing cosole output, technically you should use code templates; however that is too much stuff, and it looks bad. Your version looked bad too because console output is not represented in normal font anywhere else (that's why we have a style guide) and it looked inconsistent (also due to all those <br>s).
About Template:Keypress, of course you're not aware of Help_talk:Style/Migration_to_new_Code_formatting_templates#Template:Keypress and Help_talk:Style/Formatting_and_Punctuation#Keyboard_keys, which soon will deprecate it in favour of Template:ic; I've just applied the future rule before it goes in the style guide.
The following is my proposal, what do you think?

Launch fdisk with:

# fdisk /dev/sda

Create the first partition:

  1. Command (m for help): type n and press Enter
  2. Partition type: Select (default p): press Enter
  3. Partition number (1-4, default 1): press Enter
  4. First sector (2048-209715199, default 2048): press Enter
  5. Last sector, +sectors or +size{K,M,G} (2048-209715199....., default 209715199): type +15G and press Enter

Then create a second partition:

  1. Command (m for help): type n and press Enter
  2. Partition type: Select (default p): press Enter
  3. Partition number (1-4, default 2): press Enter
  4. First sector (31459328-209715199, default 31459328): press Enter
  5. Last sector, +sectors or +size{K,M,G} (31459328-209715199....., default 209715199): press Enter

Now preview the new partition table:

  • Command (m for help): type p and press Enter
Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5698d902

   Device Boot     Start         End     Blocks   Id  System
/dev/sda1           2048    31459327   15728640   83   Linux
/dev/sda2       31459328   209715199   89127936   83   Linux

Then write the changes to disk:

  • Command (m for help): type w and press Enter

If everything went well you can quit fdisk:

  • Command (m for help): type q and press Enter

-- Kynikos (talk) 12:30, 21 July 2013 (UTC)
Wow you are fast in doing this. I think that way it looks fantastic and will do splendidly.
-edit: one thing: fdisk will actually automatically quit after the "w" command, so i'd say
replace the last bit with: "If everything went well fdisk will now quit with the following message:"
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncinc disks. 

In case this doesn't work because fdisk encountered an error, you can use the q command to exit.

-- Bwid (talk) 16:32, 21 July 2013 (UTC)
I went ahead and put the above version into the Beginners guide.
-- Bwid (talk) 06:35, 22 July 2013 (UTC)
Well done, I didn't test it and forgot that fdisk quits after writing. -- Kynikos (talk) 09:19, 22 July 2013 (UTC)

Text shift in discussion answers

I noticed that the discussion pages of the wiki, in order to indicate that the piece of text written actually answers a comment from a guy above, we are using colon to shift our answer. The problem appears on long discussions page (like the beginner guide, I'm coming from), when we answer to answers answering answers...

I think it would be better to use a @name statement: this indicates we are answering directly to the guy whose name is written. And this avoid left space waste (especially on mobile phones, I couldn't even read the whole thread on mine yesterday, because of the so long shift). -- Wget (talk) 13:10, 5 August 2013 (UTC)

Well, about indentation we're just following Wikipedia's standards: Wikipedia:Help:Using_talk_pages#Indentation, Wikipedia:Wikipedia:Indentation.
About long discussions, outdenting can be used, Wikipedia:Wikipedia:Indentation#Outdenting.
I admit that the @ method wouldn't be such a silly idea, it would work with short discussions, but it wouldn't allow branching out long discussions. On wide screens the "left space waste" is negligible, and on my phones (Android) the browser correctly manages to fit long discussions to the screen width, I don't understand why your phone can't do that ^^
-- Kynikos (talk) 13:41, 6 August 2013 (UTC)

Talk pages of redirects

[moved to Help talk:Style#Talk pages of redirects -- Kynikos (talk) 10:01, 22 August 2013 (UTC)]

Invalid/undocumented template but it is working

Hi Kynikos! I've just noticed that, in some pages, some command statements aren't using the {{bc| YOUR COMMAND}} template, but the result is actually the same as if we have had used it.

:{{bc|$ /usr/bin/kgtk-wrapper gimp}} gives

$ /usr/bin/kgtk-wrapper gimp

$ /usr/bin/kgtk-wrapper gimp gives

$ /usr/bin/kgtk-wrapper gimp

Why is the result the same? Which one have I to choose?

Hi Wget, those are two different ways to achieve the same HTML result on the page (i.e. enclosing the content in <pre> tags); both are mentioned in Help:Style#Code formatting templates, the first one is documented in Template:bc and the second one is documented in [[Help:Editing#Code] and Help:Cheatsheet; you can choose the one you prefer, usually using a space is better for single lines of code, while using bc is better for multiple lines. -- Kynikos (talk) 02:58, 25 August 2013 (UTC)

No upstream documentation: ooops.

Sorry about that Kynikos. Is there documentation on that? I was trying to search for something regarding manpage policy but I failed to find anything. Thanks, AdamT (Talk) 20:33, 24 August 2013 (UTC)