Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Another possible fix for Terminal 'Process Complete' Apps
I recently had the old problem with the Terminal self exiting. For no reason, Terminal just started to self exit. It would echo some jibberish and then print Process Complete. But after reading the hints on this site already, found a simpler and more straight foward answer.

As I had not installed any new shells, I had no idea about why this had happened and did not want to reformat! So, poking around in com.apple.Terminal.plist (in ~/Library/Preferences), I found the ExecutionString value to be some wierd stuff. That stuff was the same stuff that Terminal echoed before it "completed its process." So making that value blank solved the problem.
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (2 votes cast)
 
[6,425 views]  

Another possible fix for Terminal 'Process Complete' | 2 comments | Create New Account
Click here to return to the 'Another possible fix for Terminal 'Process Complete'' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Another possible fix for Terminal 'Process Complete'
Authored by: SolarisSkyrider on Jul 20, '05 03:27:28PM

You are my hero. That fixed my problem, thank you!



[ Reply to This | # ]
Another possible fix for Terminal 'Process Complete'
Authored by: smitha4 on Jul 28, '05 09:40:10AM

Possible root cause of this issue: If you an a *.term file that executes a command then exists the shell, open Terminal Inspector (via the Terminal -> Window Settings... menu), and click "Use Settings as Defaults" while that *.term file is still running, then any new terminal window opened will execute the same command and exit. The reason for this behavior is the "ExecutionString" key is copied from the running *.term file to com.apple.Terminal.plist file, which is read when a new terminal window is opened.



[ Reply to This | # ]