From: Mark Harig via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 44697@debbugs.gnu.org
Subject: bug#44697: 27.1; Some typos in the Emacs Lisp (info) manuald
Date: Mon, 16 Nov 2020 19:46:10 +0000 (UTC) [thread overview]
Message-ID: <1248023439.6178613.1605555970881@mail.yahoo.com> (raw)
In-Reply-To: 1248023439.6178613.1605555970881.ref@mail.yahoo.com
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
Emacs Maintainers,
1. In (elisp) Edebug Misc, the manual states that ‘C-]’
is mapped to ‘abort-recursive-edit’. While this is
correct, that mapping is in the global-map. In
edebug-mode-map, ‘a’ is mapped to
‘abort-recursive-edit’. Also, the Edebug menu item for
“Abort” lists ‘a’, and the documentation string for
edebug-mode lists ‘a’ as mapped to
‘abort-recursive-edit’.
2. Also in (elisp) Edebug Misc, the manual states that
‘d’ is mapped to the function ‘edebug-backtrace’. There
is no function with this name in edebug.el. In Edebug
mode, ‘d’ is mapped to ‘edebug-pop-to-backtrace’.
3. In the Edebug/Views sub-menu, “View Outside Windows”
is mapped to ‘P’ (capital ‘p’), while (elisp) Edebug
Views states that ‘v’ is mapped to
‘edebug-view-outside’. In fact, both ‘P’ and ‘v’ are
mapped to this function in Edebug mode. Either the
manual should match what the sub-menu entry says, or the
sub-menu entry should be changed to match what the elisp
manual says. (Or, both should mention both keys, if
there is a reason to map both keys to the function.)
---
[-- Attachment #2: Type: text/html, Size: 4493 bytes --]
next parent reply other threads:[~2020-11-16 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1248023439.6178613.1605555970881.ref@mail.yahoo.com>
2020-11-16 19:46 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-11-16 23:17 ` bug#44697: 27.1; Some typos in the Emacs Lisp (info) manuald Lars Ingebrigtsen
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=1248023439.6178613.1605555970881@mail.yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=44697@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 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.