From: Lars Ingebrigtsen <larsi@gnus.org>
To: Samuel Bronson <naesten@gmail.com>
Cc: 17709@debbugs.gnu.org
Subject: bug#17709: 24.3; `tool-bar-map' seems inadaquately documented
Date: Sat, 12 Oct 2019 07:31:10 +0200 [thread overview]
Message-ID: <874l0emswx.fsf@gnus.org> (raw)
In-Reply-To: <87lhtb0x8n.fsf@naesten.mooo.com> (Samuel Bronson's message of "Thu, 05 Jun 2014 19:09:44 -0400")
Samuel Bronson <naesten@gmail.com> writes:
> So, we have this:
> ,----[ C-h v tool-bar-map RET ]
> | tool-bar-map is a variable defined in `tool-bar.el'.
> [...]
> | Documentation:
> | Keymap for the tool bar.
> | Define this locally to override the global tool bar.
> [...]
> `----
>
> But we also have this:
> ,----[ C-h f tool-bar-make-keymap RET ]
> | tool-bar-make-keymap is a compiled Lisp function in `tool-bar.el'.
> |
> | (tool-bar-make-keymap &optional IGNORE)
> |
> | Generate an actual keymap from `tool-bar-map'.
> | Its main job is to figure out which images to use based on the display's
> | color capability and based on the available image libraries.
> `----
>
> It seems that the docs for the variable `tool-bar-map' are, at best,
> completely glossing over the fact that, while perhaps technically a
> keymap according to the defition in (info "(elisp) Format of Keymaps"),
> the value of this variable is not actually directly usable, which
> (presumably) has some special extra conditional stuff in it that the
> `tool-bar-make-keymap' function filters out.
I've now expanded the doc string here in Emacs 27 somewhat.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-10-12 5:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 23:09 bug#17709: 24.3; `tool-bar-map' seems inadaquately documented Samuel Bronson
2019-10-12 5:31 ` Lars Ingebrigtsen [this message]
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=874l0emswx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=17709@debbugs.gnu.org \
--cc=naesten@gmail.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 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.