On 10/3/06, Axel Liljencrantz <[EMAIL PROTECTED]> wrote: > I feel that a ~/.fish configuration file makes much > more sense than a ~/.fish.d/fish file, it's too much > to write for a file that you occasionally want to > edit, and two files in ~ isn't that much.
I feel that the conceptual simplicity of having all Fish config files in one directory outweighs the cost of verbosity. I doubt that most users edit the main config file often. I rarely do; much more often I edit the function definitions in ".fish.d/". Also, filename completion shortens the typing. For exaple, it is not unreasonable to assume that you only have to write ".fi<Tab>fi", which is only two keystrokes longer than ".fish". Granted, using completion requires checking if the completion is what you want, which is an extra operation and can be distracting. Also, editors usually do not have completion; but the main Fish init file rarely appears in code or text. Also, it is easy to link to a file that you use often from your home directory, but hard to remove a hard-coded ".fish". Probably a user who wants edits a paritcular config file often already know about linking, so should not be greatly inconvenienced. As for a common directory for config files in general, I have always thought it would be much better than using $HOME, but only if most programs use it. Otherwise, every time I want to access a file, I have to check in two places. To get over the popularity hurdle, it may halp if the standard config directory initially contains links to config files in $HOME, and as each program becomes compliant, its old files in $HOME are removed. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
