This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| abstract:farber:app_dev:compute_env [2018-05-24 09:21] – [Using workgroup and directories] sraskar | abstract:farber:app_dev:compute_env [2021-04-27 16:20] (current) – [Startup and logout scripts] anita |
|---|
| |
| <code bash> | <code bash> |
| cp /etc/skel/.bash* $HOME | cp /opt/shared/templates/homedir/.bash* $HOME |
| </code> | </code> |
| <note tip>**Where to put startup commands:** You can put bash commands in either ''~/.bashrc'' or ''~/.bash_profile''. Here are general suggestions: | <note tip>**Where to put startup commands:** You can put bash commands in either ''~/.bashrc'' or ''~/.bash_profile''. Here are general suggestions: |
| It is always important to be aware of your current working directory. The standard prompt ends with the basename of ''PWD''. In these two examples the basename is the same, ''traine'', but the standard bash ''PROMPT_COMMAND'', which is executed every time you change directories, will put the full path of your current working directory in your window title. For example, | It is always important to be aware of your current working directory. The standard prompt ends with the basename of ''PWD''. In these two examples the basename is the same, ''traine'', but the standard bash ''PROMPT_COMMAND'', which is executed every time you change directories, will put the full path of your current working directory in your window title. For example, |
| |
| ''traine@farber:/lustre/work/it_css/users/traine'' | ''traine@farber:/home/work/it_css/users/traine'' |
| </note> | </note> |
| |