From: Eli Zaretskii <eliz@gnu.org>
To: mvoteiza@udel.edu, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16479@debbugs.gnu.org
Subject: bug#16479: 24.3.50; daemon freeze with tty menus
Date: Fri, 17 Jan 2014 13:59:46 +0200 [thread overview]
Message-ID: <83eh46lsy5.fsf@gnu.org> (raw)
In-Reply-To: <83fvomlv7w.fsf@gnu.org>
> Date: Fri, 17 Jan 2014 13:10:43 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 16479@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?
next prev parent reply other threads:[~2014-01-17 11:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 9:39 bug#16479: 24.3.50; daemon freeze with tty menus Mark Oteiza
2014-01-17 9:55 ` Eli Zaretskii
2014-01-17 10:21 ` Mark Oteiza
2014-01-17 11:10 ` Eli Zaretskii
2014-01-17 11:59 ` Eli Zaretskii [this message]
2014-01-17 14:55 ` Stefan Monnier
2014-01-17 15:26 ` Eli Zaretskii
2014-01-17 16:16 ` Stefan Monnier
2014-01-17 18:54 ` Eli Zaretskii
2014-01-20 17:48 ` Eli Zaretskii
2014-01-20 18:27 ` Stefan Monnier
2014-01-20 19:35 ` Eli Zaretskii
2014-01-20 20:28 ` Stefan Monnier
2014-01-20 21:17 ` Eli Zaretskii
2014-01-25 9:59 ` Eli Zaretskii
2014-01-25 22:39 ` Stefan Monnier
2014-01-26 3:52 ` Eli Zaretskii
2014-01-26 6:17 ` Stefan Monnier
2014-01-26 16:23 ` Eli Zaretskii
2014-01-27 2:07 ` Stefan Monnier
2014-02-01 9:43 ` Eli Zaretskii
2014-02-02 1:27 ` Stefan Monnier
2022-04-23 14:09 ` Lars Ingebrigtsen
2022-04-24 19:28 ` Mark Oteiza
2022-04-24 19:45 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eh46lsy5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16479@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).