unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stephen Berman'" <stephen.berman@gmx.net>, <7465@debbugs.gnu.org>
Subject: bug#7465: 24.0.50; transient-mark-mode customization UI is confusing
Date: Mon, 22 Nov 2010 08:15:00 -0800	[thread overview]
Message-ID: <4A6EC880811E4A759A6B050E7ABFE3E6@us.oracle.com> (raw)
In-Reply-To: <8739qtl6yi.fsf@escher.home>

> The complete text of the doc string is displayed, as usual, 
> but here it is confusing, because the values `lambda' and
> `(only . OLDVAL)' cannot be entered, since only toggling
> on-off is allowed.  As noted in the Elisp manual, these
> values are intended for Lisp programs, so they should not
> be mentioned in the Custom interface, which is concerned with
> user settings.

Users, even users of Customize, can also use Emacs Lisp.  The complete doc
string should always be available in Customize, and the Lisp interface should be
described in the doc string (not just the Customize interface).

However, you have a point in that the Lisp description is not identified as such
here, so this text can indeed be confusing to users.  The correct fix is to
introduce the description of the Lisp values by saying that these are the values
used in Lisp code.

Also, the text should not say that "non-nil _also_ enables highlighting...", for
this highlighting is a big part of what t-m mode is all about.  Please remove
"also" here.







  reply	other threads:[~2010-11-22 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22 15:21 bug#7465: 24.0.50; transient-mark-mode customization UI is confusing Stephen Berman
2010-11-22 16:15 ` Drew Adams [this message]
2010-12-04 21:15 ` Chong Yidong

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=4A6EC880811E4A759A6B050E7ABFE3E6@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=7465@debbugs.gnu.org \
    --cc=stephen.berman@gmx.net \
    /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).