unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 10475@debbugs.gnu.org
Subject: bug#10475: 24.0.92; `C-h v' displays `*' indicating user option
Date: Thu, 28 Apr 2016 07:16:27 -0700 (PDT)	[thread overview]
Message-ID: <3ab52fb9-48c6-4b36-a53f-fe60d607fb2d@default> (raw)
In-Reply-To: <87mvoelz66.fsf@gnus.org>

> > (defcustom foo nil
> >   "*A foobar function or nil."
> >   :type '(choice (const :tag "None" nil) function)
> >   :group 'convenience)
> >
> > Then `C-h v foo'.  The `*' indicating that this is a user variable
> > (e.g. usable by `set-variable') is printed as if it were part of the
> > doc.  It should be removed.
> 
> I don't think so.  Instead we should remove all the superfluous "*"s in
> the source code.  I'll submit a bug report.
> 
> > In addition, `user-variable-p' is the test used for functions such as
> > `set-variable', and it`user-variable-p' recognizes the `*' as defining a
> > user variable.  This is correct behavior.  The only problem is that
> > `describe-variable' should not treat this `*' as if it were part of the
> > doc text.
> 
> It no longer does that.  It's now an alias for custom-variable-p.

You're missing the point.  "It no longer does that..."
Existing code written (and usable) in earlier releases,
where `*' here DOES have that meaning and effect, should
not be handled by recent Emacs differently wrt `C-h v'.

`C-h v' should behave the same across releases in this regard.





  reply	other threads:[~2016-04-28 14:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 22:08 bug#10475: 24.0.92; `C-h v' displays `*' indicating user option Drew Adams
2016-04-28 12:01 ` Lars Ingebrigtsen
2016-04-28 14:16   ` Drew Adams [this message]
2016-04-28 16:50     ` Drew Adams

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=3ab52fb9-48c6-4b36-a53f-fe60d607fb2d@default \
    --to=drew.adams@oracle.com \
    --cc=10475@debbugs.gnu.org \
    --cc=larsi@gnus.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).