Help talk:Reading


Besides covering basic differentiations, this article could serve to improve the quality of the Wiki by avoiding repetition. How many articles say: "edit in ~/.bashrc, or zhrc (if you're using zsh) -- alternatively, edit /etc/profile.bash for system-wide changes" or something to that effect? And even though it sounds counterintuitive, expanding this article makes the Wiki better for advanced users as well, since they won't be presented with the same old information they're accustomed to skip.

We could have a basic run down of common file locations and what they mean, instead of explaining them in every article. Editors can just say "add the following to the shell's configuration" and readers would then decide whether they want it system-wide or not, etc.

Just like article:ABS is referred to in every page that involves compiling, this page could serve the same kind of utility.

—This unsigned comment is by Manolo (talk) 16:39, 12 November 2009 (UTC). Please sign your posts with ~~~~!

Meaning of comment: location in the article

The meaning of a code comment is mentioned in Help:Reading#Regular_user_or_root, which is before Help:Reading#Append.2C_add.2C_create.2C_edit linked throughout the wiki (the Create, Edit and similar redirects). -- Alad (talk) 14:38, 5 July 2016 (UTC)

And what is the problem? We can either avoid the forward reference ("Append to ~/path/to/file) in Help:Reading#Regular_user_or_root or keep the root prompts in Help:Reading#Append.2C_add.2C_create.2C_edit. -- Lahwaacz (talk) 19:02, 5 July 2016 (UTC)
The idea was that linking textedit doesn't mention comments or root prompts. By itself however, the structure of Help:Reading makes sense (if the concept of root prompt is known, demonstrating how to edit system files is easy). Perhaps we should simply generalize the redirects, pointing them to Help:Reading ? -- Alad (talk) 14:08, 26 August 2016 (UTC)

Mention tab completion?

Tab completion makes enabling services and other common commands far easier, also regarding the Installation. I've added a note to the Installation guide for now [1], but I think it's better in the long term to mention it here instead. -- Alad (talk) 14:23, 18 July 2016 (UTC)

Mentioned in [2], but maybe we should point out that some configuration will be needed (Bash#Tab_completion, Zsh#Installation/Zsh#Command completion). -- Lahwaacz (talk) 17:08, 18 July 2016 (UTC)
Another thing, what convention should we use when indicating a certain command can be tab-completed? E.g. Installation_guide#Connect_to_the_Internet uses systemctl stop dhcpcd@<TAB>. -- Alad (talk) 13:59, 11 September 2016 (UTC)

Creating directories

Since it's not a far stretch to go from "Create a file" to "Create a directory", should we add a reference to mkdir e.g. via Core utilities#mkdir ? -- Alad (talk) 12:05, 4 September 2016 (UTC)

The Help:Reading#Append, add, create, edit section heading doesn't specify "files", so a link to Core utilities#mkdir can fit in a new paragraph at the bottom. – Kynikos (talk) 09:43, 5 September 2016 (UTC)
I hope [3] is acceptable -- Alad (talk) 12:45, 5 September 2016 (UTC)
Sure is, thanks, I've taken the chance to do some more edits, closing. — Kynikos (talk) 14:43, 6 September 2016 (UTC)
Return to "Reading" page.