From: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: feedback on customize -- apropos-groups et al
Date: Sun, 10 Oct 2004 09:47:40 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICGEJNCAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1CGfR6-00030e-Ea@fencepost.gnu.org>
M-x customize RET shows you information about customize groups.
The top of the Custom buffer has a Help link to the manual's description.
You're right. Sorry, operator ignorance. Don't know how I missed the Help
button. (Button overdose, perhaps.)
3. possible to have a version of the Info section on customize
that reflects the UI on a window system?
I don't understand.
Info is text-only; the customize interface I see (with a window system) has
buttons and looks a bit different. That's all.
4. As to customize itself, it would be clearer if buttons that acted
only as
links looked like links. Buttons should be reserved for real
_actions_. Too
many buttons(!) -- most of which are not. Also, instead of having
this:
How should a link look?
Like a link in Info, for instance, or in common Web browsers. Info links
don't interfere much with reading the text. By default they are just blue
text (purple for visited links). I think this was maybe my main message:
just change buttons that are not action buttons to look like Info links. And
using a different link color for visited links ("buttons"), as in Info, also
helps navigation.
next prev parent reply other threads:[~2004-10-10 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 19:31 feedback on customize -- apropos-groups et al Drew Adams
2004-10-10 15:16 ` Richard Stallman
2004-10-10 16:47 ` Drew Adams [this message]
2004-10-10 19:14 ` Lennart Borgman
2004-10-11 16:45 ` Richard Stallman
2004-10-11 17:03 ` Drew Adams
2004-10-11 17:13 ` Lennart Borgman
2004-10-12 14:48 ` Juri Linkov
2004-10-11 16:46 ` Richard Stallman
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=DNEMKBNJBGPAOPIJOOICGEJNCAAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--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.