unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "N. Jackson" <nljlistbox2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 33320@debbugs.gnu.org
Subject: bug#33320: 27.0.50; `describe-key' fails to display help for C-mouse-3
Date: Fri, 09 Nov 2018 14:18:36 -0500	[thread overview]
Message-ID: <87tvkqkqk3.fsf@moondust.localdomain> (raw)
In-Reply-To: <83o9aybs3l.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 09 Nov 2018 09:57:50 +0200")

At 09:57 +0200 on Friday 2018-11-09, Eli Zaretskii wrote:
>
> C-mouse-3 is a kind of prefix key, and we never display
> help for prefix keys, we always wait for the user to type the complete
> key sequence, which in this case includes menu selection.

Oh, I see. That makes sense, now that you say it!

Perhaps the documentation for `describe-key' should mention that? It
might say something about it displaying that final hyphen while it is
waiting for more input, when a complete key command has not yet been
entered for it to display help on.

> You need to select one of the menu items by clicking on it, then you
> will see the help for that item.

Right. I understand that now. [Although in this case I wasn't looking
for the documentation of one of the menu items, I was looking for the
documentation for whatever function pops up the menu itself.]






  reply	other threads:[~2018-11-09 19:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 21:49 bug#33320: 27.0.50; `describe-key' fails to display help for C-mouse-3 N. Jackson
2018-11-09  7:57 ` Eli Zaretskii
2018-11-09 19:18   ` N. Jackson [this message]
2018-11-09 19:40     ` Drew Adams
2022-02-02 19:16     ` Lars Ingebrigtsen
2018-11-09 23:02   ` Richard Stallman
2018-11-10  7:49     ` Eli Zaretskii
2018-11-10 21:45     ` Glenn Morris
2018-11-12 10:16       ` Robert Pluim
2018-11-12 13:34         ` martin rudalics

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=87tvkqkqk3.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=33320@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).