all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 44577@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
	idirectscm@aim.com
Subject: bug#44577: 27.1; Missing options in definition of edebug-mode in edebug.el
Date: Thu, 12 Nov 2020 14:54:19 +0100	[thread overview]
Message-ID: <87k0uqadf8.fsf@gnus.org> (raw)
In-Reply-To: <83o8k2znzs.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Nov 2020 15:46:47 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I think we should remove the list from the doc string, yes.  It is
> unusual for a doc string of a mode to include an exhaustive list of
> all of its customization options; in general, the feature's group
> should be enough to discover all of them.  And the manual documents
> the most important ones.

The use case here is the `?' command when edebugging, which makes the
list somewhat useful.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-11-12 13:54 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
2020-11-12 13:46     ` Eli Zaretskii
2020-11-12 13:54       ` Lars Ingebrigtsen [this message]
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=87k0uqadf8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=44577@debbugs.gnu.org \
    --cc=eliz@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.