From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mark Harig <idirectscm@aim.com>
Cc: "44577@debbugs.gnu.org" <44577@debbugs.gnu.org>,
"stefankangas@gmail.com" <stefankangas@gmail.com>
Subject: bug#44577: 27.1; Missing options in definition of edebug-mode in edebug.el
Date: Thu, 12 Nov 2020 13:41:09 +0100 [thread overview]
Message-ID: <871rgybvdm.fsf@gnus.org> (raw)
In-Reply-To: <271156580.4335434.1605118597910@mail.yahoo.com> (Mark Harig's message of "Wed, 11 Nov 2020 18:16:37 +0000 (UTC)")
Mark Harig <idirectscm@aim.com> writes:
> Yes. That is the intent of the report, to get the non-existent option removed.
I've now removed this from the doc string in Emacs 28.
>> Maybe instead of maintaining a list, we should just point users to `M-x
>> customize-group RET edebug RET'. Or just remove the list and say
>> nothing.
>
> In edebug mode, type '?' to list help for the mode.
>
> This will list the keys defined for the mode followed by a list of the options.
> The options are listed as help-mode links. The links can be used to display
> help for each of the options, including their current value. This provides a
> quick method for looking up help or checking the values of the (many) edebug
> options.
Yeah, it's somewhat unconventional, but I think it's otherwise fine as is.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-12 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1575202005.4252872.1605107085622.ref@mail.yahoo.com>
2020-11-11 15:04 ` bug#44577: 27.1; Missing options in definition of edebug-mode in edebug.el Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-11 16:22 ` Stefan Kangas
2020-11-11 18:16 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-12 12:41 ` Lars Ingebrigtsen [this message]
2020-11-12 13:46 ` Eli Zaretskii
2020-11-12 13:54 ` Lars Ingebrigtsen
2020-11-12 17:46 ` Mark Harig via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-12 17:53 ` Eli Zaretskii
2020-11-14 15:33 ` 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=871rgybvdm.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44577@debbugs.gnu.org \
--cc=idirectscm@aim.com \
--cc=stefankangas@gmail.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.