hsong@nvuxl.UUCP (g hugh song) (12/20/90)
Help. This time it is not just flow control problem, I think. The symptom is like this: Whenever the emacs program issues "Quit" on the status line with the bell sound, the keyboard activity is not transfered to the host computer (DEC Station 5000/200 Ultrix 4.0) until I type F13 (LF key in VT100 mode) on the VT terminal. Curiously this only happens through DEC server hardware in combination with gnuemacs. This means It is OK on the console. It is OK through ethernet bypassing DECserver. I can exit from the emacs session by typing ^X^C [LF]. Then emacs displays the usual confirm-query on the status line asking ".. is not saved. ..save (y/n)?" So I type y [LF]. And then " ... really wnat to exit? (yes/no)?" So I type "yes [Return] [LF]". Once I get the normal shell prompt, everthing becomes normal. Yes! it becomes normal. This makes it hard to identify which side is at fault. Have you had this kind of problem before with a similar setup? What is the solution? Thanks. Please email. -hsong- nvuxl!hsong@bellcore.bellcore.com PS: On Csh command line, please type "nvuxl\!hsong@..."
hsong@munnari.oz.au (g hugh song) (12/20/90)
--text follows this line-- Help. This time it is not just flow control problem, I think. The symptom is like this: Whenever the emacs program issues "Quit" on the status line with the bell sound, the keyboard activity is not transfered to the host computer (DEC Station 5000/200 Ultrix 4.0) until I type F13 (LF key in VT100 mode) on the VT terminal. Curiously this only happens through DEC server hardware in combination with gnuemacs. This means It is OK on the console. It is OK through ethernet bypassing DECserver. I can exit from the emacs session by typing ^X^C [LF]. Then emacs displays the usual confirm-query on the status line asking ".. is not saved. ..save (y/n)?" So I type y [LF]. And then " ... really wnat to exit? (yes/no)?" So I type "yes [Return] [LF]". Once I get the normal shell prompt, everthing becomes normal. Yes! it becomes normal. This makes it hard to identify which side is at fault. Have you had this kind of problem before with a similar setup? What is the solution? Thanks. Please email. -hsong- nvuxl!hsong@bellcore.bellcore.com PS: On Csh command line, please type "nvuxl\!hsong@..."