From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: \\[...] for a mouse-event command - should never show `M-x'
Date: Sat, 23 May 2009 08:39:54 -0700 [thread overview]
Message-ID: <B0552AC6278740E5B7CAAACF83A89BFF@us.oracle.com> (raw)
`C-h v mouse-buffer-menu-mode-mult':
,----
| *Group the buffers by the major mode groups on <C-down-mouse-1>?
| This number which determines (in a hairy way) whether <C-down-mouse-1>
| will split the buffer menu by the major modes (see
| `mouse-buffer-menu-mode-groups') or just by menu length.
| Set to 1 (or even 0!) if you want to group by major mode always, and to
| a large number if you prefer a mixed multitude. The default is 4.
`----
1. Why the `?' in the first line? Typo?
2. "Mixed multitude"? "This number which determines whether..." - No verb: what
does this number (which determines...) do or mean?
This doesn't seem to be explained very well.
3. General comment -
Suppose a mouse-event command such as `mouse-buffer-menu' is not currently bound
(e.g., some code binds `C-mouse-1' to a different mouse command). Then the doc
string above shows the binding as "M-x mouse-buffer-menu", which is inaccurate
and misleading.
The user doc that explains `M-x' clearly doesn't anticipate its use to introduce
a command, such as `mouse-buffer-menu', that won't work with `M-x'. See
`(emacs)M-x'.
When the command passed (via \\[...]) to `substitute-command-keys' is known, is
there an easy way for `substitute-command-keys' to know whether the
`interactive' spec uses `e'? That wouldn't be failsafe, but it might catch most
such commands. We could then use some other indication, instead of `M-x' -
perhaps (Mouse): `(Mouse) mouse-buffer-menu'.
Or perhaps just use the command name alone: `mouse-buffer-menu'? In any case,
`M-x' is inappropriate for mouse-event commands.
next reply other threads:[~2009-05-23 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 15:39 Drew Adams [this message]
2009-05-23 17:29 ` \\[...] for a mouse-event command - should never show `M-x' Tassilo Horn
2009-05-24 10:21 ` Deniz Dogan
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=B0552AC6278740E5B7CAAACF83A89BFF@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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).