unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: xah@xahlee.org, 2473@emacsbugs.donarmstrong.com
Subject: bug#2473: usability issues on emacs's describe-mode
Date: Fri, 27 Feb 2009 18:33:29 -0500	[thread overview]
Message-ID: <E1LdCCv-0000nS-Gv@fencepost.gnu.org> (raw)
In-Reply-To: <uzlg8p2e6.fsf@gnu.org> (message from Eli Zaretskii on Fri, 27 Feb 2009 13:04:01 +0200)

    I see a 3rd way: make the buffer present an expandable list of modes,
    starting with just 2 items: the current major modes and "minor modes",
    e.g. similar to what we do in Speedbar, or maybe in Outline Mode
    (under "Hide Sublevels").  In ASCII art:

      + Major Mode: RMAIL Mode
      + Minor Modes

Using hiding is a good idea -- thanks.

I think that partcular way would be inconvenient.  Specifically, it
would be a hassle to initially hide the major mode documentation.
That is what users most often want to see; making them type a command
to expose it would be a gratuitous hassle.

So I suggest putting the partly-hidden minor mode list first,
followed by the totally visible major mode documentation.







  parent reply	other threads:[~2009-02-27 23:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 19:40 bug#2473: usability issues on emacs's describe-mode xah lee
2009-02-26 15:15 ` Stefan Monnier
2022-04-13  1:50   ` Lars Ingebrigtsen
2009-02-27 10:10 ` Richard M Stallman
2009-02-27 11:04   ` Eli Zaretskii
2009-02-27 11:31     ` Lennart Borgman
2009-02-27 15:19       ` Drew Adams
2009-02-27 23:33     ` Richard M Stallman [this message]
2009-02-27 23:56       ` Lennart Borgman
2009-02-27 23:58       ` Drew Adams
2009-02-28  4:34       ` Stefan Monnier
2009-02-28  9:12         ` xah lee
2009-02-28 10:54         ` Eli Zaretskii
2009-02-28 11:05           ` Lennart Borgman
  -- strict thread matches above, loose matches on Subject: below --
2009-03-01 11:25 Xavier Maillard

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=E1LdCCv-0000nS-Gv@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=2473@emacsbugs.donarmstrong.com \
    --cc=eliz@gnu.org \
    --cc=xah@xahlee.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).