all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 24596-done@debbugs.gnu.org
Subject: bug#24596: 25.1; `f10' behavior
Date: Thu, 06 Oct 2016 21:49:39 +0300	[thread overview]
Message-ID: <83h98pjosc.fsf@gnu.org> (raw)
In-Reply-To: <21fda037-417c-487b-b918-c6a5da1ff622@default> (message from Drew Adams on Mon, 3 Oct 2016 10:45:19 -0700 (PDT))

> Date: Mon, 3 Oct 2016 10:45:19 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 24596@debbugs.gnu.org
> 
> > > > ESC ESC works for me on MS-Windows GUI frames.
> > >
> > > For me, with emacs -Q, a single ESC cancels.  A second ESC acts as
> > > a prefix key for the next key sequence.
> > 
> > Sorry, I omitted a crucial detail: the number of ESC presses needed to
> > exit the menu depends on whether you already dropped a menu or not.
> > That is, if you press F10, then the down-arrow, to drop the File menu,
> > you need 2 ESC: the first will pop down the menu, the second will exit
> > the menu bar.  But if you just press F10, or only type right-arrow or
> > left-arrow after that, i.e. there's no menu dropped down, then just
> > one ESC is enough.
> 
> Got it.  Can the doc please say this?  I tried ESC ESC ESC with just
> f10, and I thought that the behavior was not as described.
> 
> > > > ESC ESC ESC and C-g
> > > > work for me on TTY frames.  C-g doesn't work on a GUI frame because
> > > > the menu is controlled by Windows, not by Emacs, and Windows doesn't
> > > > know about C-g.  IOW, this is a limitation we can do very little
> > > > about.
> > >
> > > OK.  Then the fix is to fix the doc, which says something quite
> > > different from what the behavior really is.
> > 
> > I can only add a note there saying that with some toolkits the exact
> > keys to exit the menu might be different.  Any better ideas?
> 
> That will help.  Thx.  Is the ESC behavior as you described above?  If
> so then it would help to mention it, I think.

I've now done that, and I'm marking this bug done.

Thanks.





  parent reply	other threads:[~2016-10-06 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<<ef8ce118-4fc8-4bc1-9606-468839196ffb@default>
     [not found] ` <<<838tu5pg0x.fsf@gnu.org>
     [not found]   ` <<c37596f6-47bc-4624-b948-c938c87bc74e@default>
     [not found]     ` <<834m4tpcsb.fsf@gnu.org>
2016-10-03 17:45       ` bug#24596: 25.1; `f10' behavior Drew Adams
2016-10-03 18:14         ` Eli Zaretskii
2016-10-06 18:49         ` Eli Zaretskii [this message]
     [not found] <<ef8ce118-4fc8-4bc1-9606-468839196ffb@default>
     [not found] ` <<838tu5pg0x.fsf@gnu.org>
2016-10-03 16:33   ` Drew Adams
2016-10-03 17:23     ` Eli Zaretskii
2016-10-03 15:41 Drew Adams
2016-10-03 16:13 ` 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=83h98pjosc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24596-done@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.