From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 50792@debbugs.gnu.org
Subject: bug#50792: 26.3; Key notation typos
Date: Sat, 25 Sep 2021 04:00:08 +0200 [thread overview]
Message-ID: <87zgs1pg7r.fsf@gnus.org> (raw)
In-Reply-To: <SJ0PR10MB5488E6B875887E69D27CAA64F3A49@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Fri, 24 Sep 2021 22:43:17 +0000")
Drew Adams <drew.adams@oracle.com> writes:
> '<ESC>-<TAB>' should instead be '<ESC> <TAB>' (as it is elsewhere in the
> manual). No modifier syntax.
Yup; fixed now.
> 2. In (emacs) Editing Binary Files:
>
> 'C-h a hexl-<RET>' should be something else. The space after C-h and
> after a doesn't mean type a SPC char, but you expect readers to see
> hexl- as meaning type those 5 chars. At least add a space before <RET>,
> but even that isn't a real fix. The notation -<...> should be used only
> following a modifier, as in M-<right>.
>
> 3. Same problem as #2, in (emacs) Mac/GNUstep Events.
I think C-h a hexl- TAB is the correct thing here, so I've made that change.
> 4. (emacs) Windows Keyboard.
>
> Is `W' introduced anywhere as a modifier key? What is 'W-<SPC>'?
I'm guessing it's "Windows key and SPC". Since it's just an example,
and it'd take too long to explain in this section, I just removed that
example.
> 5. Throuhout the Emacs manual, sometimes it's C-<BREAK>, sometimes it's
> C-<Break>. (And I don't mean in code, e.g., as an arg to `kbd'.) Is
> this correct? The contexts seem to be the same/similar: "pressing" or
> "using" such a key sequence. There are other, similar such seeming
> inconsistencies / problems with other modified function keys.
I've now regularised these to C-<Break>.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-09-25 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 22:43 bug#50792: 26.3; Key notation typos Drew Adams
2021-09-25 2:00 ` 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
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=87zgs1pg7r.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50792@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).