Re: x11 2.1.4 does not launch after update
Re: x11 2.1.4 does not launch after update
- Subject: Re: x11 2.1.4 does not launch after update
- From: Tim Cox <email@hidden>
- Date: Mon, 25 Feb 2008 15:02:27 +0100
- Keywords: CERN SpamKiller Note: -51 Charset: west-latin
Thanks for the feedback. What I said is what I meant!
Checking back, my .bashrc has contained 'set noclobber' for many years
without giving me any known trouble until Xquartz 2.1.3. Weird! Maybe
a hangover from old, old use of tcsh? :)
Likewise, my conclusion several years ago concerning which files I
needed was - as still commented in my current .bashrc:
# Non-interactive shell: if it exists, read ~/.bashrc
# Interactive login shell: if it exists, /etc/profile
# and _first_ existing of ~/.bash_profile, ~/.bash_login, ~/.profile
# Thus .bashrc is _not_ run at login (e.g. ssh connection) and I've
linked
# it from .bash_profile, which _is_ run at login.
Has this stuff changed over the years? At the time the critical thing
for me was to get .bashrc run on an ssh session. It definitely was not
getting run until I linked .bash_profile to it. I'll explore it a bit
again I've had your comments. Thanks!
Regards, Tim
On Feb 25, 2008, at 14:46 , Mark J. Reed wrote:
On Mon, Feb 25, 2008 at 6:13 AM, Tim Cox <email@hidden> wrote:
I had exactly the same situation you show in your system log and
traced it back to having 'set noclobber' in my .bashrc (which I have
soft-linked to .bash_profile in a probably futile attempt to minimize
the number of distinct startup scripts.)
I assume you mean "set -o noclobber"? The command "set noclobber"
will just replace any command line arguments that were passed to the
shell with the word "noclobber", which might indeed cause unwanted
behavior..
Also, the .bashrc gets run for every shell; if you do all your startup
stuff in it, you don't need to have a .bash_profile at all. The idea
behind the separation is more efficiency than anything. Any setup you
do that will be inherited by a subshell (e.g. you type "bash" at the
bash prompt) can be done once in the .bash_profile, which is only
executed on login. Stuff like setting up your $PATH. You put stuff
in .bashrc that isn't inherited by subshells, like aliases and set -o
options.
The upshot is that if you only want one file, you should just use
.bashrc and delete the .bash_profile altogether. Making a symlink
just means that the same commands get executed twice.
--
Mark J. Reed <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden