GNU bug report logs - #50792
26.3; Key notation typos

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Fri, 24 Sep 2021 22:44:02 UTC

Severity: normal

Found in version 26.3

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 50792 in the body.
You can then email your comments to 50792 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#50792; Package emacs. (Fri, 24 Sep 2021 22:44:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Drew Adams <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Fri, 24 Sep 2021 22:44:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>
Subject: 26.3; Key notation typos
Date: Fri, 24 Sep 2021 22:43:17 +0000
1. In (emacs) Spelling:

'<ESC>-<TAB>' should instead be '<ESC> <TAB>' (as it is elsewhere in the
manual).  No modifier syntax.

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.

'M-x ns-service-<TAB>' 

4. (emacs) Windows Keyboard.

Is `W' introduced anywhere as a modifier key?  What is 'W-<SPC>'?

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.

In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
 of 2019-08-29
Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
Windowing system distributor `Microsoft Corp.', version 10.0.19042
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''





Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#50792; Package emacs. (Sat, 25 Sep 2021 02:01:01 GMT) Full text and rfc822 format available.

Message #8 received at 50792 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 50792 <at> debbugs.gnu.org
Subject: Re: bug#50792: 26.3; Key notation typos
Date: Sat, 25 Sep 2021 04:00:08 +0200
Drew Adams <drew.adams <at> 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




bug marked as fixed in version 28.1, send any further explanations to 50792 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Sat, 25 Sep 2021 02:01:02 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 23 Oct 2021 11:24:11 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 158 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.