From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 14797@debbugs.gnu.org
Subject: bug#14797: 24.3.50; new, undocumented menu structure using VECTORS?
Date: Sat, 06 Aug 2016 09:09:50 -0400 [thread overview]
Message-ID: <87d1lm6o2p.fsf@users.sourceforge.net> (raw)
In-Reply-To: <ac88bffa-6837-4e58-a194-ab19793bc4b1@default> (Drew Adams's message of "Fri, 5 Jul 2013 08:17:57 -0700 (PDT)")
[-- Attachment #1: Type: text/plain, Size: 182 bytes --]
tags 14797 patch
quit
Drew Adams <drew.adams@oracle.com> writes:
> What was gained by this?
I guess it's for efficiency?
Anyway, it might as well be documented, how about this:
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1218 bytes --]
From 6dd01ff617b3ee8ef8ad307a7776c2142f7f02ed Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Sat, 6 Aug 2016 09:05:05 -0400
Subject: [PATCH v1] Document use of vectors in keymaps
* doc/lispref/keymaps.texi (Format of Keymaps): Mention vector
format (Bug #14797).
---
doc/lispref/keymaps.texi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index f5d3811..a47d790 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -199,6 +199,14 @@ Format of Keymaps
bindings. A keymap with such a char-table is called a @dfn{full
keymap}. Other keymaps are called @dfn{sparse keymaps}.
+@item @var{vector}
+This kind of element is similar to a char-table: element @var{n} is
+the binding for the character with code @var{n}. Since the range of
+characters that can be bound this way is limited by the vector size,
+and vector creation allocates space for all character codes from 0 up,
+this format should not be used except for creating menu keymaps
+(@pxref{Menu Keymaps}), where the bindings themselves don't matter.
+
@item @var{string}
@cindex keymap prompt string
@cindex overall prompt string
--
2.8.0
next prev parent reply other threads:[~2016-08-06 13:09 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1lm6o2p.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=14797@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=monnier@iro.umontreal.ca \
/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.