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


Click here to return to the 'Revisiting Terminal.app's [Process completed] bug' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Revisiting Terminal.app's [Process completed] bug
Authored by: gid on Mar 15, '06 12:58:29AM

Unfortunately, the new zsh didn't seem to work for me. I compiled 4.3.2 from source, expecting it to solve the problem (as it has for me before), and it still happened occasionally.

As far as I can tell, the fault isn't with zsh per se, as bash also suffers from the same problem: it seems to be a problem with "login" and the allocation of ttys. As a result, this solution gets round it by making the zsh NOT a login shell as such.



[ Reply to This | # ]
Revisiting Terminal.app's [Process completed] bug
Authored by: gid on Mar 15, '06 01:05:45AM

Sorry, SethTisue, I just reread your comment, and realised my reply didn't directly answer it. Yes, I tried that too. Or at least, I rebooted (I had pending software updates anyway), and then tapped Cmd-N about twenty times, Cmd-W the same number of times (repeat as needed) to try to trigger the error. That should've cleared up the ttys as you describe, but it didn't work.

For some reason, this recent reinstall of my iBook has had a few quirks... the tenaciousness of this bug being one of them.



[ Reply to This | # ]
Revisiting Terminal.app's [Process completed] bug
Authored by: SethTisue on Mar 17, '06 07:35:22AM

Trying to fix all the tty's at once by tapping Command-N twenty times doesn't work; you'd think it would but in my experience it doesn't necessarily do it. I don't understand why. But that's the first thing I tried too and it doesn't necessarily fix the problem right away. Nonetheless, the bug eventually stopped happening on every Mac I've tried this on. Be patient. DON'T go back to the old zsh, stick with the new one for a while, and I believe that your problem will eventually go away.

Oh, one more thing: how absolutely, completely sure are you that you are actually running the new binary and not the old one? How do you know?

One more thing: I'm actually running 4.2.6, not 4.3. (Apple bundles 4.2.3.) While it seems unlikely that 4.3.2 would have the bug if 4.2.6 doesn't, if you're desperate you could try 4.2.6.



[ Reply to This | # ]