GNU bug report logs - #16479
24.3.50; daemon freeze with tty menus

Previous Next

Package: emacs;

Reported by: Mark Oteiza <mvoteiza <at> udel.edu>

Date: Fri, 17 Jan 2014 09:40:02 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #17 received at 16479 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: mvoteiza <at> udel.edu, Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 16479 <at> debbugs.gnu.org
Subject: Re: bug#16479: 24.3.50; daemon freeze with tty menus
Date: Fri, 17 Jan 2014 13:59:46 +0200
> Date: Fri, 17 Jan 2014 13:10:43 +0200
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 16479 <at> debbugs.gnu.org
> 
> > With menu-bar-mode (and thus the new tty menus) enabled, if I do the
> > steps I outlined above, I expect to be able to return to the previous
> > client and finish input.  This is not the case: if I go back to the
> > first client with the menu, and try an arrow key or C-{npbf}, emacs
> > crashes.  I think this is a bug.
> 
> A crash is always a bug.
> 
> I understand that you are talking about the situation where the menu
> is already open on one client, and then you start another client.
> 
> If so, this seems to have something to do with the fact that starting
> a client writes something to the terminal (to query the terminal about
> its features).

I tried to fix this in trunk revision 116053.  It is still not ideal
(but what _is_ the ideal in this case?): the open menu pops down, and
you need to type C-g in the client where the menu was open to get out,
but at least the daemon doesn't segfault.

Stefan, can you suggest a better solution?




This bug report was last modified 3 years and 86 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.