Re: X PATH variable
Re: X PATH variable
- Subject: Re: X PATH variable
- From: Doug McNutt <email@hidden>
- Date: Wed, 15 Jan 2003 21:15:55 -0700
At 17:55 -0500 1/15/03, Joel Hacker wrote:
>It's true that by default there is no /etc/csh.login, but if you create one then Terminal reads it.
Yes. I didn't get the name right; it's /etc/csh.login that gets executed and overwrites the .plist specification for PATH. And it gets executed (sourced) by tcsh rather than directly by Terminal. It's a matter of entering tcsh in login or stand-alone mode.
Apple's Jaguar installer creates an /etc/csh.login like this:
# begin
# System wide login for csh(1)
setenv PATH "/bin:/sbin:/usr/bin:/usr/sbin"
# end
and it doesn't even think about the .plist which came before it.
Is the presence of that file a bug? Should it be simply deleted? If I delete it will Apple put it back? Does X11 in some way depend on it? What happens if I telnet - er ssh - to the Mac from a dumb terminal? Are there things that depend on /etc/csh.login being there and that I can't fix in my personal .login?
If I add an item to the existing path in an tcshrc file do I get multiple instances of directories when the tcshrc is sourced at different SHLVL's? AppleScript enters at SHLVL = 2! If I run a BBEdit worksheet or execute a commend in Project Builder the login file isn't executed at all. Neither the one in /etc/ nor my own in $HOME/.
--
--> In Christianity, man can have only one wife. This is known as monotony. <--
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe: http://www.lists.apple.com/mailman/listinfo/x11-users
Do not post admin requests to the list. They will be ignored.