Revision as of 21:29, 29 December 2013

Contents

Invocation and config files

Right now the overview and sourcing order of config files is combined in a confusing way. I've tried to merge a redundant section called startup files from further down the page. Here is what I envision:

bash-completion

I first put "complete -cf sudo" in my .bashrc and much later installed bash-completion. This combination makes the completion go insane, for example "sudo cp <tab>" lists all files and folders in the current directory and several thousand things in my PATH. Should a warning be included in the article in the section about bash-completion to remove/comment "complete ..." lines from .bashrc? -Markus00000 08:36, 9 November 2011 (EST)

Colors for "command not found"

Recently User:Grufo restored the colors with [2] and the following summary:

"discouraged" doesn't mean "forbidden": HTML tags here are useful to emphasize the difference between the two packages, also about colors. See the Color Bash Prompt page to be convinced.

Color Bash Prompt has to use colors because colors are the main topic of the article that gives it its reason to exist. This doesn't happen to the Bash#The "command not found" hook section, whose purpose is to mention the existence of those hooks, not to attempt providing "screenshots". Moreover, the red color used in the alternative hook is purely aesthetic and doesn't carry any particular meaning for the user, who can safely ignore it (not to mention the colors in the prompts).

Besides Grufo's reply, it would be interesting to also read the opinion of other users. -- Kynikos (talk) 02:58, 4 December 2013 (UTC)

Hi!

I wrote my opinion… it's just an opinion. Let's see what do the other users say…! --Grufo[ contribs | talk ] 13:06, 4 December 2013 (UTC)

I have to agree with Kynikos - why not just keep it simple? The colors in the relevant section are mainly for the fancy prompt, the red "abiword" could be (and was in the previous revision) highlighted in bold instead. By your arguments every command on ArchWiki could have a fancy colored prompt - this conflicts with the current style conventions. If you want to propose changes to the conventions or some template like Template:hc, refer to the relevant talk page. -- Lahwaacz (talk) 15:20, 4 December 2013 (UTC)

It is not just about style. The complex HTML code also make it hard for future update and translation. I think no other users could edit this section anymore. --Fengchao (talk) 12:57, 8 December 2013 (UTC)