From: Stefan Kangas <stefan@marxist.se>
To: Tassilo Horn <tsdh@gnu.org>
Cc: 18992@debbugs.gnu.org
Subject: bug#18992: 24.4; describe-mode
Date: Thu, 05 Dec 2019 12:35:29 +0100 [thread overview]
Message-ID: <87tv6ff1j2.fsf@marxist.se> (raw)
In-Reply-To: <871tpdvk10.fsf@thinkpad-t440p.tsdh.org> (Tassilo Horn's message of "Sat, 08 Nov 2014 15:34:03 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> Well, but of course having the mode functions printed in `describe-mode'
> wouldn't hurt anyway. This patch does that:
[...]
> With that, in this message buffer I get:
>
> Message mode (`message-mode') defined in `message.el':
> Major mode for editing mail and news to be sent.
> Like Text Mode but with these additional commands:
I don't think this is an improvement. It risks confusing more than it
helps, especially for beginning users.
We can already say `C-h v major-mode RET' which to my mind is wholly
sufficient for anyone who needs to know the value of the `major-mode'
variable.
> With the following patch, the same would be done for the active minor
> modes, too:
[...]
> However, in contrast to major-modes, minor mode names tend to be much
> longer, so we can get some long lines like:
>
> Global-Edit-Server-Edit minor mode (`global-edit-server-edit-mode'; no indicator):
I think this is even less of an improvement.
I suggest to close this as wontfix. If I don't see any objections,
I'll just go ahead and do that within a couple of weeks. Please send
any opinions on this issue before then.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-12-05 11:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 9:16 bug#18992: 24.4; describe-mode Andreas Röhler
2014-11-08 14:34 ` Tassilo Horn
2014-11-08 15:54 ` Andreas Röhler
2014-11-08 16:35 ` Drew Adams
2014-11-08 15:57 ` Drew Adams
2014-11-08 16:42 ` Drew Adams
2019-12-05 11:35 ` Stefan Kangas [this message]
2020-01-15 2:01 ` 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=87tv6ff1j2.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=18992@debbugs.gnu.org \
--cc=tsdh@gnu.org \
/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).