all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: RE: Use faces to indicate states in Customize?
Date: Tue, 15 Feb 2005 09:10:59 -0800	[thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBKEDACMAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200502150148.j1F1mE006139@raven.dms.auburn.edu>

       (each entry here is (1) proposed text, (2) state, (3) current
       text, (4) doc string text from `custom-magic-alist'):

    The entries you give for (4) to not seem to correspond either to
    today's recent or yesterday's values of `custom-magic-alist'.

No, they are older - sorry for any confusion in that regard. The exact text
is not relevant to my point, however.

My point was to continue to provide info such as that in (3) and (4), but to
do so only upon request (e.g. via tooltip), in order to reduce the text
displayed for each custom option.

There are relatively few custom "states". A long description of each state
need not be repeated each time the state is mentioned. My idea is to use 1)
only a short name (label) at each state occurrence and 2) a "legend" that
accurately describes what each such label stands for.

The legend could be in a centralized location (e.g. buffer bottom) and could
describe all of the states (once), or it could be available only upon demand
and be split up, as a set of individual tooltips for the state names. I
prefer the latter, but either is better than repeating a description at each
occurrence, IMO.

The other part of my idea is to use color to make the states easier to
distinguish when scanning.

      reply	other threads:[~2005-02-15 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11 21:10 Use faces to indicate states in Customize? Drew Adams
2005-02-15  1:27 ` Luc Teirlinck
2005-02-15  1:48 ` Luc Teirlinck
2005-02-15 17:10   ` Drew Adams [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=FDELKNEBLPKKDCEBEJCBKEDACMAA.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.