unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'martin rudalics' <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: RE: option doc strings and Customize tags
Date: Wed, 29 Oct 2008 11:33:57 +0900	[thread overview]
Message-ID: <87hc6wf7u2.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <005201c93933$6bd2eb30$0200a8c0@us.oracle.com>

Drew Adams writes:

 > A more general formatting problem is that the Lisp values might be
 > quite long.

Maybe.  This is possibly a YAGNI, though.  What I'm thinking is that
normally long values will either be indirect (eg, the value of
variable whose name can be used instead of the value), or they will be
compounds in which case a compound widget will be used so that the
components can be changed.

Even if there are a small number, the "indirection through variable"
workaround might be more appropriate (DRY: you can use C-h v on the
variable name and get its value and docstring easily) and easier to
implement than more general formatting.




  parent reply	other threads:[~2008-10-29  2:33 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
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 [this message]
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

  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=87hc6wf7u2.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --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 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).