On Jan 8, 2008 6:09 PM, Isaac Dupree <[EMAIL PROTECTED]> wrote: > Axel Liljencrantz wrote: [...] > >>> This conflicts with > >>> the assumptions some people have when writing startup scripts that the > >>> cwd is ~. Fish solves this by cd:ind to ~, calling the startup scripts > >>> and the cd back to wherever cwd was before the startup scripts. > >>> > >>> This unfortunatly makes your rather sane and reasonable expectations > >>> fail. Perhaps it would be a better tradeof to never change the cwd and > >>> let broken startup scripts fail? > >> actually they don't execute in '~', but in '~/.config/fish' (on my fish > >> anyway) (I guess this makes broken startup scripts fail immediately, so > >> their owners can fix them without getting too confused usually). I > >> guess it would be a little more consistent to just execute them without > >> messing with the cwd (which would basically solve my problem... I guess > >> I would say "if we're interactive and in ~, go to my preferred > >> directory", which seems pretty safe). > > > > True. Back in the day, the fish config file was located in ~. The fact > > that no one has complained should be an indication that the issue is > > not to serious. I'll put changing this on my todo. > > Thanks
Done. Patch is in the darcs tree. Axel > > ~Isaac > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
