From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: describe-mode's treatment of minor-modes is annoying
Date: Tue, 4 May 2004 10:05:00 -0400 [thread overview]
Message-ID: <20040504140500.GC23709@fencepost> (raw)
In-Reply-To: <m1n04oz4h1.fsf-monnier+emacs@gnu.org>
On Tue, May 04, 2004 at 09:52:03AM -0400, Stefan Monnier wrote:
> >> I think all that should be moved to _after_ the major mode description,
> >> with a single-line hyper link at the beginning of the buffer that jumps
> >> there.
> > I second that; the new behavior is annoying as hell.
>
> Well, I don't know about hell, but I agree in the sense that I find it
> unhelpful. Maybe we should not only move the minor mode summary to after
> the major mode, but also split the minor mode summary into buffer-local
> minor modes vs global minor modes.
Yeah I agree about that too; if the minor modes are on their own page after
the major modes, I think it would suffice to just put the global modes after
the local modes, with a blank line or two in between them, just enough to
make the separation clear.
-Miles
--
Come now, if we were really planning to harm you, would we be waiting here,
beside the path, in the very darkest part of the forest?
next prev parent reply other threads:[~2004-05-04 14:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 4:05 describe-mode's treatment of minor-modes is annoying Miles Bader
2004-05-04 8:21 ` Juanma Barranquero
2004-05-04 11:53 ` Romain Francoise
2004-05-04 13:52 ` Stefan Monnier
2004-05-04 14:05 ` Miles Bader [this message]
2004-05-04 14:38 ` Romain Francoise
2004-05-04 20:08 ` Richard Stallman
2004-05-04 20:58 ` Drew Adams
2004-05-04 21:16 ` Stefan Monnier
2004-05-04 22:35 ` Miles Bader
2004-05-05 20:20 ` Richard Stallman
2004-05-05 20:32 ` Drew Adams
2004-05-06 8:42 ` Juri Linkov
2004-05-04 22:28 ` Miles Bader
2004-05-05 20:21 ` Richard Stallman
2004-05-05 22:06 ` Miles Bader
2004-05-06 11:49 ` Richard Stallman
2004-05-06 13:52 ` Miles Bader
2004-05-06 16:40 ` Peter Whaite
2004-05-07 12:09 ` Thien-Thi Nguyen
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=20040504140500.GC23709@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@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).