From: Andreas Schwab <schwab@linux-m68k.org>
To: Karl Fogel <kfogel@openitp.org>
Cc: 12309-done@debbugs.gnu.org
Subject: bug#12309: Option `(bookmark-)version-control': Use :tag so doc string matches menu
Date: Mon, 01 Oct 2012 11:41:50 +0200 [thread overview]
Message-ID: <m2y5jqv89t.fsf@igel.home> (raw)
In-Reply-To: <87r4pihn0e.fsf@floss.red-bean.com> (Karl Fogel's message of "Sun, 30 Sep 2012 22:47:13 -0500")
Karl Fogel <kfogel@openitp.org> writes:
> I don't fully understand the whole customization system because I never
> use it myself (I just read doc strings and set variables directly in
> Elisp), so I don't quite get what `other' mean if used instead of
> `const', and I didn't fully understand the last paragraph of the
> original bug report. I looked in the Info pages, but they didn't
> clarify much about this.
const only matches the specified value, other matches any value, but
uses the specified value when setting. Thus setting the variable
manually to 'foo won't get a mismatch. You can see the documentation of
each widget with widget-browse.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-10-01 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 22:57 bug#12309: 24.2.50; Option `(bookmark-)version-control': Use :tag so doc string matches menu Drew Adams
2012-09-16 23:32 ` bug#12309: 24.2.50; Option `(bookmark-)version-control': Use :tag so doc string matchesmenu Drew Adams
2012-10-01 3:47 ` bug#12309: Option `(bookmark-)version-control': Use :tag so doc string matches menu Karl Fogel
2012-10-01 9:41 ` Andreas Schwab [this message]
2012-10-01 21:25 ` Karl Fogel
2012-10-01 4:17 ` bug#12309: Improved wording Karl Fogel
2012-10-01 4:37 ` bug#12309: Option `(bookmark-)version-control': Use :tag so doc string matches menu Karl Fogel
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=m2y5jqv89t.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=12309-done@debbugs.gnu.org \
--cc=kfogel@openitp.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 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).