Description of Problem: After SOME emacs sessions are exited, the terminal may be in a bad state. While the program functions normally, with no ill effects, after leaving the program, the terminal may have poor settings for ^D, ^C, ^H, ^J and may no longer echo command line entry to the screen. Version-Release number of selected component (if applicable): 20.7-41 How Reproducible: Sometimes Steps to Reproduce: 1. rlogin to system. The problem happens more often with rlogin, but terminal problems can occur with SSH. 2. run emacs. Perform operations that mofidy large portions of the screen - rebuild an RPM, for instance, or seomthing else that clears the screen. 3. Exit emacs. Terminal is now messed up. Actual Results: Misbehaving terminal, as described. Expected Results: Terminal settings similar to that of a fresh login Additional Information: This may be a terminal problem and not a setup problem.
I use emacs extensively, and have never seen that... probably a terminal problem. Reopen if you can provide a reprodusible testcase on a known-good terminal (i.e. windows telnet doesn't count ;).
Hmm. Can windows DO rlogin? 8-)
Same as Teg. I am addicted to emacs and I cannot reproduce this bug on my rawhide linux box. But I have already seen this kind of bug in the past, caused by a broken /bin/login.
I'll see if I can cook up a procedure guaranteed to set it off then.