$SHELL
$SHELL
- Subject: $SHELL
- From: David Borman <email@hidden>
- Date: Fri, 11 Sep 2009 17:55:10 -0500
Ok, I don't use the standard /bin/sh as my login shell, I've used /bin/
csh for years, old habits die hard. :-)
I'm running SnowLeopard X11. When I fire up X11, my xterms all get
started with /bin/sh as the shell. This is because when they start,
the environment variable "SHELL=/bin/sh" is set. If I unset SHELL
from my environment and then fire up an xterm, it properly looks up my
login shell info and starts up the session with /bin/csh.
I also start up two xterm sessions out of my .xinitrc, and at the end
start up quartz-wm. In my .xinitrc, if I add a "unset SHELL" command,
then the two xterm sessions that I start up have /bin/csh, and SHELL
is not set.
But, any xterm sessions that I then start up from the X11 application
menu still have SHELL=/bin/sh, so the xterms come up with /bin/sh
instead of /bin/csh.
Does anyone know where SHELL is getting initially set, and any idea
why it isn't getting it properly pulled out of my login information?
It's been a long time since I've looked into the inner workings in
this area, is quartz-wm the one that actually fires off the items from
the X11 applications menu? If so, then it appears that quartz-wm is
improperly initializing SHELL, since I've guaranteed that SHELL is not
set when quartz-wm is started. I tried modifying the
org.x.X11.login_shell variable, but setting that to /bin/csh didn't
appear to have any effect.
This all worked just fine under Leopard. :-(
-David Borman
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden