unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mvoteiza@udel.edu, 16479@debbugs.gnu.org
Subject: bug#16479: 24.3.50; daemon freeze with tty menus
Date: Sun, 26 Jan 2014 05:52:33 +0200	[thread overview]
Message-ID: <83bnyzbdry.fsf@gnu.org> (raw)
In-Reply-To: <jwvtxcrlmfa.fsf-monnier+emacsbugs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: mvoteiza@udel.edu,  16479@debbugs.gnu.org
> Date: Sat, 25 Jan 2014 17:39:16 -0500
> 
> >   emacsclient -t
> > This pops down the menu, but the value of
> > overriding-terminal-local-map in the original frame is not restored,
> > so, for example, any cursor motion command signals an error because it
> > tries to invoke tty-menu commands.
> > What am I not doing correctly here?  TIA.
> 
> Maybe there's a bug in our handling of let-binding w.r.t terminal-local
> variables (i.e. the unbind of overriding-terminal-local-map ands up
> resetting that variable in the new terminal rather than in the terminal
> where the specbind was done).
> 
> I can't remember seeing code to handle that when I last touched the
> let-binding code, so it sounds very likely: we try and handle
> buffer-local and frame-local correctly (by remembering where the
> binding was installed a de-install it at the right place) but we don't
> do that same thing for terminal-local bindings.

Could this be related to the fact that Voverriding_terminal_local_map
is a per-keyboard variable?





  reply	other threads:[~2014-01-26  3:52 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
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 [this message]
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=83bnyzbdry.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).