From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Help buffer link on name of customizable thing (at start of buffer)
Date: Mon, 21 Aug 2006 23:08:43 -0400 [thread overview]
Message-ID: <E1GFMd9-0003LT-Md@fencepost.gnu.org> (raw)
In-Reply-To: <MEEKKIABFKKDFJMPIOEBKEDMDEAA.drew.adams@oracle.com>
In buffer *Help*, for help on a thing that is customizable, put the same
link on the name of the customizable thing (e.g. user variable or face), at
the beginning of the *Help* buffer, that is currently put on the word
"customize" at the bottom of the buffer.
Advantage: When you use, say, `C-v some-option', you can hit RET
immediately, to customize the thing, since the cursor is at `point-min' by
default. This is quicker than using, e.g., `M-x customize-option': instead
of `M-x customize-option RET foo RET', just use `C-h v foo RET RET'.
I see no harm in it. Does anyone else object?
Also, the same form (i.e., the same *Help* buffer layout) should be used for
faces and user options. This is not the case now. Currently, `describe-face'
puts a "(customize this face)" link right after the face name, on the first
*Help* buffer line, whereas `describe-variable' puts a "You can customize
this variable" link at the bottom of the buffer, just before the [back]
button. The latter form is preferable, IMO.
I did describe-face that way for a reason. The face-spec data is
usually big enough that it won't fit on the screen. If we put "You
can customize this face" at the end, the user would not initially see
it. For describe-variable, that CAN happen, but it is rare.
There is no problem in principle with putting at the top
for variables, just as it is for faces.
next prev parent reply other threads:[~2006-08-22 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-20 19:34 Help buffer link on name of customizable thing (at start of buffer) Drew Adams
2006-08-22 3:08 ` Richard Stallman [this message]
2006-08-22 3:52 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1GFMd9-0003LT-Md@fencepost.gnu.org \
--to=rms@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.