Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
scripting:bashbehaviour [2015/08/04 10:02]
thebonsai [Interactive shell] interactive shells and login-shells aren't mutual exclusive
scripting:bashbehaviour [2015/08/04 10:03]
thebonsai [Interactive shell] still typo DOH!
Line 35: Line 35:
 ==== Interactive shell ==== ==== Interactive shell ====
  
-When Bash starts as an interactivenon-loginshell, it reads and executes commands from ''​~/​.bashrc''​. This file should contain, for example, aliases, since they need to be defined in every shell as they'​re not inherited from the parent shell.+When Bash starts as an interactive non-login shell, it reads and executes commands from ''​~/​.bashrc''​. This file should contain, for example, aliases, since they need to be defined in every shell as they'​re not inherited from the parent shell.
  
 The feature to have a system-wide ''/​etc/​bash.bashrc''​ or a similar system-wide rc-file is specific to vendors and distributors that ship //their own, patched variant of Bash//. The classic way to have a system-wide rc file is to ''​source /​etc/​bashrc''​ from every user's ''​~/​.bashrc''​. The feature to have a system-wide ''/​etc/​bash.bashrc''​ or a similar system-wide rc-file is specific to vendors and distributors that ship //their own, patched variant of Bash//. The classic way to have a system-wide rc file is to ''​source /​etc/​bashrc''​ from every user's ''​~/​.bashrc''​.
  • scripting/bashbehaviour.txt
  • Last modified: 2015/08/04 10:03
  • by thebonsai