Son of a gun! You are correct. Thank you for the suggestion!
I renamed the .tcshrc file so it would not load, and now TM will execute the python and perl stuff just fine using <command>r.
I've tried to debug this file, but never found anything wrong with it. Indeed, all environment variables and set variables load fine. It certainly doesn't bail out before reaching the end. Is it possible that this sets a variable that TM doesn't expect?
Here is the script (I am sure the mail server will wrap lines where they are not really wrapped). I would be grateful if someone would point out my mistakes.
#!/bin/tcsh setenv CVSROOT "/usr/local/cvsroot" setenv PYLIB /System/Library/Frameworks/Python.framework/Versions/Current/lib/python2.5 setenv JAVA_HOME /Library/Java/Home setenv ANT_HOME /usr/local/ant setenv PATH /usr/local/ant/bin:$PATH setenv MYSQL_HOME /usr/local/mysql setenv PATH /usr/local/mysql/bin:$PATH setenv EDITOR "/Users/broz/bbeditshell.sh" setenv PYTHONDOCS /Developer/Documentation/Python
# for subversion setenv PATH /usr/local/bin:$PATH setenv LC_CTYPE "en_US.UTF-8" setenv LANG "en_US.UTF-8"
# for darwinPorts
setenv PATH /opt/local/bin:/opt/local/sbin:$PATH # for X11 # setenv DISPLAY :0.0
# for ctags alias btags '/usr/local/bin/ctags --excmd=number --tag-relative=no --fields=+a+m+n+S -R `pwd`'
# source /usr/share/tcsh/examples/rc
# history stuff # does not work. wish it did # set savehist=(99 merge) # set autolist # bindkey -k page-down history-search-forward # bindkey -k page-up history-search-backward # history keys # bind '"M-e": history-search-backward' # bind '"M-r": history-search-forward' # Setting PATH for MacPython 2.5 # The orginal version is saved in .cshrc.pysave
set path=(/Library/Frameworks/Python.framework/Versions/Current/bin $path)
# according to http://tcshrc.sourceforge.net/, # I'm supposed to add this line due to a bug source $HOME/.tcshrc.local
some time around 7.8.2007 3:51 PM, someone named Robin Houston at robin.houston@gmail.com typed these words:
Last time someone had a similar-sounding problem, it was because they had something in their .tcshrc that failed when the current working directory was not the home directory. The easy way to test for this is to rename your .tcshrc so that tcsh can't find it, and see if the problem goes away.
If that works, go through your .tcshrc and try to find the mistake. If you can't, then post it here, and I'm sure one of us will be able to help.
Robin
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate