On Thu, Mar 25, 2010 at 17:44, chombee <[email protected]> wrote: > I'm trying to share as much of my shell configuration as possible between > shells by putting it in files that are evaluated by each shell. For example > I moved all my aliases into ~/.aliases and added . ~/.aliases to my fish > config file. The alias command seems to be compatible, so other shells > should be able to source the same aliases file. > > My fish config file also has a lot of variables set with the set or set -x > command. From reading the man files of sh and bash and doing a quick test > with bash, fish's set syntax does not seem to be supported by other shells. > One work-around that sidesteps the problem is to set environment variables in only one shell and always launch the other shell(s) from it. This only helps for environment variables. * Shell variables are mostly shell-specific settings anyway and can't be shared. * Aliases can be handled as you already do. Also, try to write standalone scripts instead of aliases where possible.
P.S. generally in fish, there is much less point to use the config file - see "Initialization file, and why you don't need it" in http://fishshell.org/wiki/moin.cgi/BashToFish However, this seems like a step backward for your arrangement of shared config; i'm just mentioning it in case in you switch to fish completely one day -- Beni Cherniavsky-Paskin <[email protected]> ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
