From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 18649@debbugs.gnu.org
Subject: bug#18649: 25.0.50; Closing TTY menus on MS-Windows
Date: Tue, 07 Oct 2014 18:46:29 +0300 [thread overview]
Message-ID: <83oatnlw6i.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0hFXr2EmczwW+OYHk1X_q8cUrCXdmZj_bU1cUbKtLjE9g@mail.gmail.com>
> Date: Tue, 7 Oct 2014 08:50:39 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
>
> Recipe:
> emacs -Q -nw
> F10 C-g
>
> C-g should close/exit the TTY menu, but it doesn't.
>
> If I start to type something, the TTY menu dissapears, but the cursor is
> not visible anymore.
There's nothing wrong with TTY menus: ESC ESC ESC still pops the menu
down, as does clicking the mouse somewhere outside the menu.
The problem is with C-g: it somehow shortcuts too much, and bypasses
the code that was supposed to be seen by the menu displaying
functions. For example, try "C-h k C-g": all you will see is "Quit"
in the echo area, but no help. IOW, we throw to top level too early
or too radically.
I don't see this on GNU/Linux, probably again because the low-level
details of keyboard input are different.
The problem started somewhere between trunk revisions 117575 and
117589. I have trunk binaries from these two revisions, and the
former still works correctly. Unfortunately, this range of revisions
includes the jumbo changeset related to pixel-wise resizing, which at
the very least makes it easy to drown in the flood and miss the
important parts.
If someone has time to bisect more accurately, or debug this, or even
give an idea where to look, you are welcome.
next prev parent reply other threads:[~2014-10-07 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 6:50 bug#18649: 25.0.50; Closing TTY menus on MS-Windows Dani Moncayo
2014-10-07 15:46 ` Eli Zaretskii [this message]
2014-10-07 19:58 ` Eli Zaretskii
2014-10-08 9:32 ` martin rudalics
2014-10-08 10:29 ` Eli Zaretskii
2014-10-08 12:49 ` Eli Zaretskii
2014-10-08 13:13 ` Dani Moncayo
2014-10-08 13:35 ` martin rudalics
2014-10-08 13:57 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83oatnlw6i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18649@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.