From: Mark Harig via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 58325@debbugs.gnu.org
Subject: bug#58325: 28.1: Function-name error in documentation of M-j key binding
Date: Thu, 6 Oct 2022 02:18:13 +0000 (UTC) [thread overview]
Message-ID: <1276150927.2947857.1665022693435@mail.yahoo.com> (raw)
In-Reply-To: 1276150927.2947857.1665022693435.ref@mail.yahoo.com
1. In the Emacs info manual, (emacs) Comment Commands, there is
the sentence:
`C-M-j'
`M-j'
Like `<RET>' followed by inserting and aligning a comment
(`comment-indent-new-line').
However, C-h c M-j reports (for numerous (all?) major modes)
M-j runs the command default-indent-new-line
Although the function `comment-indent-new-line' exists, the key
sequences C-M-j and M-j are not bound to it.
So, the sentence in the Emacs info manual needs to have
`comment-indent-new-line' changed to `default-indent-new-line'.
2. In the Emacs info manual, (emacs) Multi-Line Comments, there
is the sentence:
If you are typing a comment and wish to continue it to
another line, type `M-j' or `C-M-j'
(`comment-indent-new-line').
This sentence, too, needs to be changed to list the correct
function name (`default-indent-new-line').
3. Note also that only the second instance of
`comment-indent-new-line' is found with an index search, and
the match is not the definition of the key binding:
Found ‘comment-indent-new-line’ in Command Index. (Only match)
With the fix described above, an index entry should be added to
find `default-indent-new-line' in (emacs) Comment Commands.
(End of report.)
next parent reply other threads:[~2022-10-06 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1276150927.2947857.1665022693435.ref@mail.yahoo.com>
2022-10-06 2:18 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-06 7:34 ` bug#58325: 28.1: Function-name error in documentation of M-j key binding Stefan Kangas
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=1276150927.2947857.1665022693435@mail.yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58325@debbugs.gnu.org \
--cc=idirectscm@aim.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).