unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org, rms@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: describe-mode's treatment of minor-modes is annoying
Date: Tue, 4 May 2004 18:35:17 -0400	[thread overview]
Message-ID: <20040504223517.GC10432@fencepost> (raw)
In-Reply-To: <FDELKNEBLPKKDCEBEJCBGEECCEAA.drew.adams@oracle.com>

On Tue, May 04, 2004 at 01:58:35PM -0700, Drew Adams wrote:
> 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.

I think that the major-mode doc should _always_ be displayed.  In most cases
I think that's what people are interested in, and _always_ having to follow a
hyperlink to get at it would just be annoying (and I think in practice it
would be _always_, too, as there's usually some random minor mode or another
turned on).

However, maybe it would be a good idea to separate the minor mode
descriptions as you say, and just include a hyper link that described them
(using the format I gave in my earlier message, with a single line at the
beginning of the major-mode description).  There could be a [back] button at
the beginning of the minor-mode help to allow easily jumping back and forth.

That way it wouldn't waste any time formatting all that minor mode stuff in
the common case, and a user could even invoke `describe-minor-modes'
directly if that's what he was really interested in.

Hmmm, I like it...

-Miles
-- 
`Suppose Korea goes to the World Cup final against Japan and wins,' Moon said.
`All the past could be forgiven.'   [NYT]

  parent reply	other threads:[~2004-05-04 22:35 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 [this message]
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=20040504223517.GC10432@fencepost \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).