On Jul 9, 2007, at 9:07 PM, Joseph Ayers wrote: However, I lit up Terminal in the virgin account then switched to my main account, started Terminal and lo and behold, it started up with the bash prompt and executes my .term file elegantly.
The only thing I can spot in com.apple.Terminal.plist that could cause the problem you describe would be the chosen start-up .term file, specifically its ability to specify the login shell (that is, the preferences field labeled "Execute this command (specify complete path):"). If you set that to something that terminates right away, then you'd get what you describe. And of course, you report that your problem began when you were fooling with .term files, so that's at least the same neighborhood. If you're really curious, you should explore that old .term file (if you still have it). They're text (XML, actually), so you should be able to examine it with something simplistic like "more" or "pico" or "vi" or "emacs" or "textedit" or "textmate", whatever your favorite tool may be for reading just plain old text.
-==-
Jack RepenningChief Technology Officer CollabNet, Inc. 8000 Marina Boulevard, Suite 600 Brisbane, California 94005 office: +1 650.228.2562 mobile: +1 408.835.8090 raindance: +1 877.326.2337, x844.7461 aim: jackrepenning skype: jrepenning
|