You're right - sloppy wording on my part. More accurate would be
"for-terminal-use". For example, $PS1 and other terminal related stuff.
That is,things I want set typically for all terminal instances.
That's based on the bash manpage I read somewhere back on Solaris years
ago. It said that .bashrc was sourced upon shell invocation whereas
.bash_profile was sourced only at login. For my purposes that essentially
made .bashrc work for terminal sessions. For others it might be different.
Like I said you'll see different approaches.
... man, that was tough to type on my phone, with dot file names and auto
correct / auto predict! :-)
Len Philpot
lphilpo...@gmail.com
Sent from my Android phone using AqualMail Pro
On January 8, 2017 10:11:57 AM Ulli Horlacher
<frams...@rus.uni-stuttgart.de> wrote:
On Sun 2017-01-08 (10:02), Len Philpot wrote:
For bash, I usually put per-terminal-instance values in ~/.bashrc
No good idea, because *every* bash subshell will execute ~/.bashrc, not
only when you start a new terminal program!
You can see it, when you add the line
echo executing ~/.bashrc
into your ~/.bashrc
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<d85c358b-1096-f24e-ad04-a0e25a5f5...@gmail.com>
--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
--
xubuntu-users mailing list
xubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/xubuntu-users
