From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: 25505@debbugs.gnu.org
Subject: bug#25505: 24.5; doc of `define-minor-mode': incorrect for :keymap
Date: Fri, 10 Feb 2017 18:28:32 -0500 [thread overview]
Message-ID: <8737flmxr3.fsf@users.sourceforge.net> (raw)
In-Reply-To: <a1069da8-bd14-4f68-964a-b6a88b65b0d5@default> (Drew Adams's message of "Sat, 21 Jan 2017 10:24:11 -0800 (PST)")
tags 25505 notabug
quit
Drew Adams <drew.adams@oracle.com> writes:
> 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.
The doc says "variable name" as opposed to "expression", I think it's
clear that expression will be evaluated, and something which is not an
expression will not be evaluated. I guess we could add "it should be an
unquoted variable name..."
>
> So, for example, the `define-minor-mode' fr `follow-mode' uses this:
>
> :keymap follow-mode-map
This is correct, follow-mode-map is the name of the variable.
> and not this:
>
> :keymap 'follow-mode-map
This is not correct, it's an expression which evaluates to the name of
the variable.
>
> 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)
This is correct, it's an expression which evaluates to a keymap.
> 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?
I don't see why, it's a macro, some arguments are evaluated, some
aren't.
> Here is allout.el, for example. It DOES use a quoted map-variable
> (and it jumps through a few hoops).
I don't think it should be doing that, it seems to be using some kind of
needlessly complicated trickery.
> Next up: autoarg-mode. This uses an UNquoted map variable.
That's correct.
> Those are only the first two grep hits for `define-minor-mode'.
I checked a few more at random, I found no more incorrect cases.
next prev parent reply other threads:[~2017-02-10 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 18:24 bug#25505: 24.5; doc of `define-minor-mode': incorrect for :keymap Drew Adams
2017-01-23 17:12 ` Drew Adams
2017-02-10 23:28 ` npostavs [this message]
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
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=8737flmxr3.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25505@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).