From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: describe-mode's treatment of minor-modes is annoying
Date: 07 May 2004 08:09:50 -0400 [thread overview]
Message-ID: <jkhdusfng1.fsf@glug.org> (raw)
In-Reply-To: Peter Whaite's message of "Thu, 06 May 2004 12:40:34 -0400"
Peter Whaite <emacs@whaite.ca> writes:
inline the description of its corresponding mode rather than
displaying it in another buffer?
reading this reminds me of similar presentation style, using
outline, for buffer-local variables, as implemented in:
http://www.glug.org/people/ttn/software/ttn-pers-elisp/dist/
lisp/low-stress/print-buffer-local-variables.el
it seems to me for a flat set of items numbering less than 100
(such as buffer-local variables, or contemporaneous major/minor
modes), outline as top-level presentation format is ideal.
particular outline style as well as what to do w/ each item --
hiding, hyperlinking, further decoration -- can be considered as
separate questions.
thi
prev parent reply other threads:[~2004-05-07 12:09 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
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 [this message]
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=jkhdusfng1.fsf@glug.org \
--to=ttn@glug.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).