[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#34785: 26.1; fake function-key typos
From: |
Drew Adams |
Subject: |
bug#34785: 26.1; fake function-key typos |
Date: |
Fri, 8 Mar 2019 09:08:34 -0800 (PST) |
> tags 34785 notabug
> thanks
>
> > Date: Thu, 7 Mar 2019 17:28:19 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> >
> > (elisp) `Modifying Menu' has an example that uses fake function keys
> > <drink> and <eat>, but it writes these as <DRINK> and <EAT>.
>
> That is correct, since key labels are up-cased. Cf. <RET>, <DEL>,
> etc.
>
> This is not a bug.
Elsewhere in the manual, "fake function key" refers
to the symbol itself - e.g., in node `Menu Bar':
"the fake function key 'menu-bar'"
Not `<menu-bar>'. And not `<MENU-BAR>'.
"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.)
"Here, 'edit' is the fake function key"
"a list of fake function keys.... The default value
is '(help-menu)'"
Not `(<help-menu>)'. And not `<HELP-MENU>'.
And in node `Tool Bar':
"fake function key called 'tool-bar'"
Not `(<tool-bar>)'. And not `<TOOL-BAR>'.
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.