From: Drew Adams <drew.adams@oracle.com>
To: npostavs@users.sourceforge.net
Cc: 14797@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#14797: 24.3.50; new, undocumented menu structure using VECTORS?
Date: Sat, 6 Aug 2016 09:52:07 -0700 (PDT) [thread overview]
Message-ID: <febdf846-7686-46f4-99b9-b04de278ab0c@default> (raw)
In-Reply-To: <87vazd6ekh.fsf@users.sourceforge.net>
> > It's not very clear to me from this doc what the relation
> > is between a key binding and a "binding for the character".
> > Keys and characters are different animals. Clearly there
> > is a relation between them here, but it doesn't seem to
> > be made explicit.
>
> I think it's clear from the text in `(elisp) Key Sequences':
>
> A "key sequence", or "key" for short, is a sequence of one or more
> input events that form a unit. Input events include characters,
Maybe. (But "character" is also something other than an input
event, even for Emacs.)
But it is still "not very clear to me from _this_ doc".
A few words clarifying that might help. Or a cross-ref to
the doc that covers it.
> > But again, unless you want to try to clarify that, the
> > proposed doc is OK, and adding it improves things.
next prev parent reply other threads:[~2016-08-06 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 23:54 bug#14797: 24.3.50; new, undocumented menu structure using VECTORS? Drew Adams
2013-07-05 10:42 ` Stefan Monnier
2013-07-05 15:17 ` Drew Adams
2013-07-05 22:45 ` Stefan Monnier
2013-07-06 1:40 ` Drew Adams
2013-10-19 17:48 ` Drew Adams
2016-08-06 13:09 ` npostavs
2016-08-06 14:42 ` Eli Zaretskii
2016-08-06 15:42 ` Noam Postavsky
2016-08-06 17:36 ` Eli Zaretskii
2016-08-06 19:53 ` npostavs
[not found] ` <<87d1lm6o2p.fsf@users.sourceforge.net>
[not found] ` <<83k2fuj6vp.fsf@gnu.org>
2016-08-06 16:15 ` Drew Adams
2016-08-06 16:35 ` npostavs
2016-08-06 16:52 ` Drew Adams [this message]
2016-08-06 17:40 ` 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
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=febdf846-7686-46f4-99b9-b04de278ab0c@default \
--to=drew.adams@oracle.com \
--cc=14797@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.net \
/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).