From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: RE: custom type `color' is not enforced
Date: Thu, 20 Dec 2007 22:47:39 -0800 [thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACMEOMCFAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1J5Z2p-0000lh-Lf@fencepost.gnu.org>
> Don't assume that the user knows just which option s?he wants
> to describe. `describe-variable' gives you only one way, by
> option name, to define a set of candidate options, in order
> to pick one to describe.
>
> I'm not assuming that. Rather, I don't think very many people
> would take the trouble to remember that `describe-option-of-type'
> exists. Thus, practically speaking it would not be very useful.
It needs a binding, yes. Not very many people would have learned or would
remember several of the help commands if they were not bound.
FWIW, in my code, I use these bindings in `help-map':
`o' for `describe-option' (= `describe-variable' with prefix arg)
`C-o' for `describe-option-of-type'
`c' for `describe-command' (= `describe-function' with prefix arg)
(`describe-key-briefly' is `C-c'.)
next prev parent reply other threads:[~2007-12-21 6:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DNEMKBNJBGPAOPIJOOICAELMEBAA.drew.adams@oracle.com>
2007-12-18 23:00 ` custom type `color' is not enforced Drew Adams
2007-12-20 0:53 ` Richard Stallman
2007-12-20 1:27 ` Lennart Borgman (gmail)
2007-12-21 3:04 ` Richard Stallman
2007-12-20 19:11 ` Drew Adams
2007-12-20 19:27 ` Drew Adams
2007-12-21 3:59 ` Richard Stallman
2007-12-21 6:47 ` Drew Adams [this message]
2007-12-21 3:59 ` Richard Stallman
2007-12-21 6:48 ` Drew Adams
2007-12-21 9:36 ` Lennart Borgman (gmail)
2007-12-21 18:20 ` Drew Adams
2007-12-21 22:03 ` Drew Adams
2007-12-22 6:29 ` Richard Stallman
2007-12-22 20:58 ` Lennart Borgman (gmail)
2007-12-23 10:54 ` Per Abrahamsen
2007-12-23 12:46 ` Lennart Borgman (gmail)
2007-12-25 13:52 ` Per Abrahamsen
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=BNELLINCGFJLDJIKDGACMEOMCFAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--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).