[Pythonmac-SIG] Running Python scripts without full paths
Paul Berkowitz
berkowit@silcom.com
Sat, 30 Nov 2002 14:09:24 -0800
On 11/30/02 1:30 PM, "Nicholas Riley" <njriley@uiuc.edu> wrote:
> No, just everything that sets your path - that's what we're after!
The man pages for tcsh say this:
A login shell begins by executing commands from the system
files /etc/csh.cshrc and /etc/csh.login. It then executes
commands from files in the user's home directory: first
~/.tcshrc (+) or, if ~/.tcshrc is not found, ~/.cshrc,
then ~/.history (or the value of the histfile shell vari-
able), then ~/.login, and finally ~/.cshdirs (or the value
of the dirsfile shell variable) (+). The shell may read
/etc/csh.login before instead of after /etc/csh.cshrc, and
~/.login before instead of after ~/.tcshrc or ~/.cshrc and
~/.history, if so compiled; see the version shell vari-
able. (+)
The "infamous" /usr/share/tcsh/examples/README says:
----------
In order to use this configuration:
echo "source /usr/share/tcsh/examples/rc" > ~/.tcshrc
echo "source /usr/share/tcsh/examples/login" > ~/.login
echo "source /usr/share/tcsh/examples/logout" > ~/.logout
To do this system-wide, do the same instead to /etc/csh.cshrc,
/etc/csh.login, and /etc/csh.logout.
----------------------
(which is not English and doesn't make any sense. "In order to use this
configuration", do what? Which configuration? Makes no sense.)
It also says:
-------
See the corresponding file in /usr/share/init/tcsh for more information
about the role of each file.
--------------
There _is no such file_. In fact, there is no /usr/share/init/ directory at
all.
It look like I'll have to do what Kevin did (thanks, Kevin). From the
README:
-----------------
In order to customize tcsh:
mkdir ~/Library/init/tcsh
and create the following files there as necessary:
aliases.mine - shell aliases
completions.mine - completions
environment.mine - environment
rc.mine - run commands
path - command search path
-------------
using 'path', and just trust that some other shells don't overwrite the PATH
environment variable as set in ~/.MacOS/environment.plist.
There's certainly something messy here.
--
Paul Berkowitz