From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 34785@debbugs.gnu.org
Subject: bug#34785: 26.1; fake function-key typos
Date: Sat, 09 Mar 2019 13:24:32 +0200 [thread overview]
Message-ID: <83d0n08f4f.fsf@gnu.org> (raw)
In-Reply-To: <d6d1d2d3-80e6-435e-8925-89590b9db3f0@default> (message from Drew Adams on Fri, 8 Mar 2019 09:08:34 -0800 (PST))
> Date: Fri, 8 Mar 2019 09:08:34 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 34785-done@debbugs.gnu.org
>
> Elsewhere in the manual, "fake function key" refers
> to the symbol itself
Some of those are bugs, some not.
> e.g., in node `Menu Bar':
>
> "the fake function key 'menu-bar'"
>
> Not `<menu-bar>'. And not `<MENU-BAR>'.
Fixed.
> "To add an item to the menu bar, invent a fake function key of your
> own (let's call it KEY), and make a binding for the key sequence
> '[menu-bar KEY]'."
>
> Not `<KEY>'. (And KEY is a placeholder here.)
Exactly, and so it shouldn't be marked up as a key.
> "Here, 'edit' is the fake function key"
I fixed this in a different way.
> "a list of fake function keys.... The default value
> is '(help-menu)'"
>
> Not `(<help-menu>)'. And not `<HELP-MENU>'.
Here help-menu is a symbol in a list, so the markup is correct.
> And in node `Tool Bar':
>
> "fake function key called 'tool-bar'"
>
> Not `(<tool-bar>)'. And not `<TOOL-BAR>'.
Fixed.
> The bug I cited is the only place where the treatment
> is different, whether or not you argue that `<EAT>'
> there is a key label.
That place uses the correct markup.
Thanks.
next prev parent reply other threads:[~2019-03-09 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<64eb34fd-633f-4c51-9fde-7dfc1bbc4151@default>
[not found] ` <<83h8cda3m4.fsf@gnu.org>
2019-03-08 17:08 ` bug#34785: 26.1; fake function-key typos Drew Adams
2019-03-09 11:24 ` Eli Zaretskii [this message]
2019-03-08 1:28 Drew Adams
2019-03-08 13:37 ` 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=83d0n08f4f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34785@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 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.