From: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: describe-mode's treatment of minor-modes is annoying
Date: Tue, 4 May 2004 13:58:35 -0700 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBGEECCEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1BL6D8-0003QY-4u@fencepost.gnu.org>
> I think it used to put the minor modes after the major mode. The
> problem was, people did not even know the minor mode info was there.
In Emacs 20, the first two lines said this:
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.
>> E.g., make the layout something like:
>> (Information on [minor modes] comes after the major mode
description)
> This might be ok. It should also suggest typing C-x ] C-x ] to get to
> the minor mode information. That should always work, since the major
> mode doc string should never contain a page break.
C-x ] and C-x [ are not obvious. And the pages are all displayed together
(at least in Emacs 20): ^L is all that appears as page separator, so the
buffer is quite busy.
Instead of using separate pages in the same buffer, why not use separate
incarnations of the *Help* buffer. `C-h m' would display just a one-liner
about each mode in *Help*, with a link for each mode (part or all of the
one-liner) to its detailed description:
Major mode
SQL[oracle] mode: Major mode to edit SQL.
Minor modes
Font-Lock minor mode (no indicator): Toggle Font Lock mode.
...
If there are no minor modes, just show the major-mode doc directly.
The links would display the individual mode descriptions in *Help*, with a
back button. Less busy. Uses links instead of C-x ] to navigate.
Drawback: cannot see (or print) everything at once. Would that be worth
another link/button that displays everything at once (separate pages)?
- Drew
next prev parent reply other threads:[~2004-05-04 20:58 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 [this message]
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=FDELKNEBLPKKDCEBEJCBGEECCEAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--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).