> On Aug 24, 2017, at 8:04 AM, David Adam <zanc...@ucc.gu.uwa.edu.au> wrote: > >> On Wed, 23 Aug 2017, Mark Volkmann wrote: >> I want to make sure I understand when this should be used. Is this correct? >> >> PATH should be configured in config.fish. >> >> fish_user_paths should be set from a terminal in order to make a change >> that will affect all current sessions without having to modify config.fish >> and source it in all the current and future sessions. >> >> I understand that fish_user_paths is a universal variable and changes to it >> will persist. But it seems that if really want a permanent change that is >> easy to find later, I should modify PATH in config.fish. If I wanted to see >> my path customizations later, my first instinct would be look at my >> config.fish rather echoing fish_user_paths. >> >> Looking for clarification > > Hi Mark, > > Have a look at https://github.com/fish-shell/fish-shell/issues/527 which > documents the design process.
Thanks! I wonder if this is a good set of guidelines related to this. 1) Feel free to set PATH in config.fish, but you don't have to because fish doesn't "require" configuration. 2) Do not set fish_user_paths in config.fish. 3) Setting PATH in config.fish is preferred if you may want to copy your configuration to another machine later. 4) Setting fish_user_paths from a terminal is fine if you will only ever need that setting on the current machine and when you want to examine the PATH later, you can remember that fish_user_paths affects it. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
