Terminal.app
Brian Wolven
bcwolven at jhu.edu
Mon Mar 10 07:46:07 PDT 2008
LuKreme wrote:
> On 9-Mar-2008, at 15:40, Eugene wrote:
>> Besides the usual wiping of ~/Library/Application Support/Terminal/*
>> and ~/Library/Preferences/com.apple.Terminal.plist, have you checked
>> your login scripts to see if they are invoking something goofy? The
>> AEProcessAppleEvent invocation... AppleScript?
>
>
> I've removed preferences, but not the application support file
> (default.term) because, frankly, I forgot it existed.
>
> That seems to have sorted it, thanks. (well, as long as I don't try to
> open a third tab :/)
>
> (and no, I don't have any login scripts, the file must have just been
> corrupt)
I had issues with terminal like this a while back; opening up
~/Library/Preferences/com.apple.Terminal.plist, I found that an entry
entitled "ExecutionString" contained instructions to cd to a particular
directory, probably left there by an applescript that I run as a finder
extension (opens terminal in the directory you are currently viewing).
In the event that that directory no longer exists, well... problems
happen. Deleting the contents of that entry solved the problem.
More information about the MacOSX-talk
mailing list