Re: emacs lockup w/ TERM = linux (cygwin tty deadlock)
On Mon, Nov 18, 2002 at 02:07:59PM -0500, Joe Buehler wrote: >Christopher Faylor wrote: > >>Btw, this appears to be some kind of deadlock in the pty code. >> >>Maybe Egor or Sergey or Steve O will want to investigate? > >If it's apropos, emacs is using the pty functions in libutil >supplied by inetutils. I already found the problem and offered an rxvt fix. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: emacs lockup w/ TERM = linux (cygwin tty deadlock)
Christopher Faylor wrote: Btw, this appears to be some kind of deadlock in the pty code. Maybe Egor or Sergey or Steve O will want to investigate? If it's apropos, emacs is using the pty functions in libutil supplied by inetutils. Joe Buehler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: emacs lockup w/ TERM = linux (cygwin tty deadlock)
On Fri, Nov 15, 2002 at 05:35:22PM -0500, Christopher Faylor wrote: >On Fri, Nov 15, 2002 at 10:32:25PM +, David Starks-Browning wrote: >>On Friday 15 Nov 02, Bill Priest writes: >>> All, >>> Another piece of the puzzle. >>> >>> if TERM = linux inside rxvt (windows version) then >>> emacs hangs while loading the lisp files; status line >>> freezes on "Loading international/mule-cmds..." >> >>OK, there is indeed something wierd going on with TERM=linux. Not as >>you describe, but the screen fills with ;2cl; (or something like that) >>and C-x C-c doesn't work. I can't attach with strace. This is Win98. > >Doctor, doctor... Btw, this appears to be some kind of deadlock in the pty code. Maybe Egor or Sergey or Steve O will want to investigate? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
