From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'martin rudalics' <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: RE: option doc strings and Customize tags
Date: Tue, 28 Oct 2008 13:25:01 -0700 [thread overview]
Message-ID: <005401c9393b$41ee26b0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <e01d8a50810281303g39c45c6u75bf8f46f10737b0@mail.gmail.com>
> >> >> > nil Case-sensitive
> >> >> > t Case-insensitive
> >> >> > <other> Use default
> >> >>
> >> >> I'd put the Lisp values in parentheses as
> >> >>
> >> >> Case-sensitive (nil)
> >> >> Case-insensitive (t)
> >> >> Use default
> >> >
> >> > Sure, fine, whatever. It doesn't matter much what format we
> >> > use. Except that adding parens might confuse things for Lisp
> >> > values that are lists: ((foo bar)).
> >> >
> >> > A more general formatting problem is that the Lisp values
> >> > might be quite long. Some kind of abbreviation is probably
> >> > called for.
> >>
> >> A link that is opened in *Help* and shows the value with an
> >> explanation where it came from?
> >
> > Possibly. But the point here is to show all of the possible
> > values *together*. You don't want to click a button/link and
> > open *Help* for each possible value, to see its Lisp value
> > separately from the others.
> >
> > A single display of all tags and their Lisp values (in
> > *Help* or elsewhere) is what's needed. See the original
> > suggestion.
>
> I meant that for the long values only. But the buffer that shows the
> long value can show all the values together.
If it shows all of the values together, then there is no sense in showing it
"for the long values only". The point is to show all of the values, for
comparison and comprehension, whenever you try to look at any of them (even a
short one). For the need to see the values together, it's irrelevant whether a
value is long or short.
Perhaps you are saying that if all values are short enough then no separate
display is needed - they can be shown in the menu. But if even one value is long
(whatever "long" means), then a separate display is needed.
next prev parent reply other threads:[~2008-10-28 20:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 18:12 option doc strings and Customize tags Drew Adams
2008-10-28 19:09 ` martin rudalics
2008-10-28 19:28 ` Drew Adams
2008-10-28 19:38 ` Lennart Borgman
2008-10-28 19:49 ` Drew Adams
2008-10-28 20:03 ` Lennart Borgman
2008-10-28 20:25 ` Drew Adams [this message]
2008-10-28 20:29 ` Lennart Borgman
2008-10-30 5:01 ` Kevin Rodgers
2008-10-30 6:06 ` Lennart Borgman
2008-10-29 2:33 ` Stephen J. Turnbull
2008-10-29 6:45 ` Drew Adams
2008-10-29 14:36 ` Stefan Monnier
2008-10-29 16:08 ` Drew Adams
2008-10-29 17:17 ` Stefan Monnier
2008-10-30 1:42 ` Stephen J. Turnbull
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='005401c9393b$41ee26b0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=rudalics@gmx.at \
/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.