unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: RE: describe-mode's treatment of minor-modes is annoying
Date: Wed, 5 May 2004 13:32:41 -0700	[thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBEEENCEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1BLSsy-0004zW-AJ@fencepost.gnu.org>

Yes, I checked it in vanilla (GNU) Emacs 20.7 (emacs -q).

       The major mode is described first.
       For minor modes, see following pages.

    So users knew the minor mode info was there, and they saw the major mode
    info first.

> If you've checked this, you're surely correct.  But I remember that the
> minor mode info was not very visible, and not easy to use.  That was
> the reason for the change.

I too think the minor (and major!) mode info was not very visible - because
everything was visible together, separated only by ^L. And not very easy to
use, because users needed to know about C-].

Even a horizontal bar (a la <HR> in HTML) would be a better separator
visually than ^L.

 - Drew

  reply	other threads:[~2004-05-05 20:32 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
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 [this message]
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=FDELKNEBLPKKDCEBEJCBEEENCEAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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).