No argument of any sort was made in #8, specious or otherwise; only an
observation.
"And placing "profiley" stuff into bashrc slows down the shell (as if
it's not slow enough already!)"
Adding things to PATH that you want access to in all your interactive
shells, belongs in the file sourced by in
That was absolute bull. Ubuntu obviously ships with /etc/profile, which
is a "version" of bash_profile, so #8 was a specious argument. And
placing "profiley" stuff into bashrc slows down the shell (as if it's
not slow enough already!)
Some .xsessionrc file (or whatever is read by the *dm's) must m
As an end user, then, you should add ~/bin/ to your path from within
.bashrc, rather than .bash_profile. It has long been historical practice
for xterms and the like not to spawn login shells by default. For this
reason, people have for many years followed the practice of placing
anything important
(I'll just add here that FWIW Ubuntu does not in fact ship with
.bash_profile at all, just the .bashrc)
--
newly opened gnome-terminal windows don't have .bash_profile sourced
https://bugs.launchpad.net/bugs/17962
You received this bug notification because you are a member of Ubuntu
Bugs, which i
So this has been reported a number of times in different guises .. for
example:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/72714
which links us back to:
http://bugzilla.gnome.org/show_bug.cgi?id=150521
Which shows that the gnome folk are not interested in fixing this.
So as a distribut
This is not a bug; newly started terminal emulators should not start
login shells, since they are already part of a login session. They are
correct in running sh/bash as a non-login shell, which is the same
behavior as would be observed when, for example, starting an escape
shell from the ftp/telne
