[prev] [thread] [next] [lurker] [Date index for 2006/08/25]
> The bastard X server isn't using that, and is (or at least as far as all
> the documentation and preferences goes) hard coded to start xterm.
It starts whatever the CMD-N item is on the "File" menu, which is normal
for OS X applications. Sorta. Unless they're by Microsoft or Adobe or
even Apple now and start a whiny wizard... [insert hate here]
I don't know whether I like this or not, because I have a long-running
love-(turned-to-hate)-hate relationship with the various X11 session
startup files from boring-but-rational old .xinitrc through the preversions
that CDE foisted upon us.
Add to that the various other ways that a shell can get started without it
being a login shell or inheriting a sane environment...
[I'd go on, but it's an old, dry hate, hadly worth the effort]
I gave up on .login long since, and have a .cshrc that starts something
like
if ( ! $?LOGINSHELL ) then
setenv LOGINSHELL $$
# .. proceed with "this is my first shell, act like a login shell" stuff
if ( $?prompt ) then
tset -e -k
# ... etc
endif
set path=($path ~/bin /usr/local/bin /sw/bin /opt/local/bin)
# ... etc
endif
I'm sure something similar could be arranged for folks who prefer [kb]ou?rne?
(again)? shells.
Generated at 03:01 on 31 Aug 2006 by mariachi 0.52