Size: 672
Comment: bash --rcfile /my/custom/bashrc
|
Size: 1077
Comment: Dear Linux people: not everyone is on Linux. Sincerely, the rest of the world.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
[[Anchor(faq23)]] == I want to launch an interactive shell that has a special set of aliases and functions, not the ones in the user's ~/.bashrc. == |
<<Anchor(faq23)>> == I want to launch an interactive shell that has special aliases and functions, not the ones in the user's ~/.bashrc. == Just specify a different start-up file: |
Line 8: | Line 9: |
Or: {{{ bash --rcfile <(printf %s 'my; commands; here') }}} Or, if you happen to be on Linux: {{{ ~ $ bash --rcfile /dev/fd/3 -i 3<<<'cowsay moo' _____ < moo > ----- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || +bash-4.3$ exit exit }}} |
|
Line 10: | Line 33: |
Put {{{exec bash}}} at the end of it to launch an interactive shell. This shell will inherit the environment (which does ''not'' include aliases, but that's OK, because [#faq80 aliases suck]). Of course, you must also make sure that your script runs in a terminal -- otherwise, you must create one, for example, by using {{{exec xterm -e bash}}}. | Put {{{exec bash}}} at the end of it to launch an interactive shell. This shell will inherit the environment (which does ''not'' include aliases, but that's OK, because [[BashFAQ/080|aliases suck]]). Of course, you must also make sure that your script runs in a terminal -- otherwise, you must create one, for example, by using {{{exec xterm -e bash}}}. ---- CategoryShell |
I want to launch an interactive shell that has special aliases and functions, not the ones in the user's ~/.bashrc.
Just specify a different start-up file:
bash --rcfile /my/custom/bashrc
Or:
bash --rcfile <(printf %s 'my; commands; here')
Or, if you happen to be on Linux:
~ $ bash --rcfile /dev/fd/3 -i 3<<<'cowsay moo' _____ < moo > ----- \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || +bash-4.3$ exit exit
Variant question: I have a script that sets up an environment, and I want to give the user control at the end of it.
Put exec bash at the end of it to launch an interactive shell. This shell will inherit the environment (which does not include aliases, but that's OK, because aliases suck). Of course, you must also make sure that your script runs in a terminal -- otherwise, you must create one, for example, by using exec xterm -e bash.