From: Drew Adams <drew.adams@oracle.com>
To: 25505@debbugs.gnu.org
Subject: bug#25505: 24.5; doc of `define-minor-mode': incorrect for :keymap
Date: Sat, 21 Jan 2017 10:24:11 -0800 (PST) [thread overview]
Message-ID: <a1069da8-bd14-4f68-964a-b6a88b65b0d5@default> (raw)
For :keymap, the doc string says "Same as the KEYMAP argument."
Similarly the doc in (elisp) `Defining Minor Modes'. This does not
appear to be correct.
For positional arg KEYMAP, the doc string says:
If non-nil, it should be a variable name (whose value is a keymap),
or an expression that returns either a keymap or a list of
arguments for `easy-mmode-define-keymap'.
...
But the value of :keymap apparently cannot be a variable name whose
value is a keymap or an expression that evaluates to a keymap. The
:keymap value you pass is apparently not evaluated - unlike other
keyword values such as :group.
So, for example, the `define-minor-mode' fr `follow-mode' uses this:
:keymap follow-mode-map
and not this:
:keymap 'follow-mode-map
and not this:
(let ((mainmap (make-sparse-keymap))
(map (make-sparse-keymap)))
(define-key map "\C-v" 'follow-scroll-up)
...
(define-key mainmap follow-mode-prefix map)
(define-key mainmap [remap end-of-buffer] 'follow-end-of-buffer)
...
mainmap)
In fact, it is not clear from the doc whether and which keyword values
are evaluated. And shouldn't they all be evaluated or else none be so?
In GNU Emacs 24.5.1 (i686-pc-mingw32)
of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/usr --host=i686-pc-mingw32'
next reply other threads:[~2017-01-21 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 18:24 Drew Adams [this message]
2017-01-23 17:12 ` bug#25505: 24.5; doc of `define-minor-mode': incorrect for :keymap Drew Adams
2017-02-10 23:28 ` npostavs
2017-02-10 23:43 ` Drew Adams
2017-02-15 14:49 ` Michael Heerdegen
2017-02-15 16:55 ` Noam Postavsky
2021-09-25 16:12 ` Stefan Kangas
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=a1069da8-bd14-4f68-964a-b6a88b65b0d5@default \
--to=drew.adams@oracle.com \
--cc=25505@debbugs.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 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.