unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Glenn Morris'" <rgm@gnu.org>, <emacs-devel@gnu.org>
Subject: RE: What version of Emacs still requires '*' in defcustom docs?
Date: Sat, 11 Feb 2012 15:33:10 -0800	[thread overview]
Message-ID: <F6EB9EB31449486280586DA81F239691@us.oracle.com> (raw)
In-Reply-To: <nu4nuxx9rh.fsf@fencepost.gnu.org>

> > Eg GNU Emacs has not needed this since at least 21.1 (see 
> > user-variable-p).

Yes, and it was 21.1 that _introduced_ the bug (#10475), which is still there.
Two steps forward, one step back.  Half-baked.
 
> PS 21.1 is over 10 years old.

So are some Emacs users. ;-)

Does it bother you that `C-h v' should have to accommodate a leading `*' for a
user variable, even though `defcustom' no longer _requires_ a leading `*'?  All
it has to do is ignore (strip) it.  What's the big deal?  The fix is trivial,
and is provided in the bug report.

Besides, `C-h v' needs to do the same thing _anyway_ for a user variable defined
this way:

(defvar toto 42 "*This IS a user var. Always has been.")

`toto' is a user variable, as defined and recognized by `user-variable-p' (which
you cited) and as recognized by `set-variable'.

Circulez ; il n'y a rien a voir.




  reply	other threads:[~2012-02-11 23:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11 22:29 What version of Emacs still requires '*' in defcustom docs? Glenn Morris
2012-02-11 22:49 ` Drew Adams
2012-02-11 22:53 ` Glenn Morris
2012-02-11 23:33   ` Drew Adams [this message]
2012-02-12 10:16 ` Chong Yidong
2012-02-12 15:42   ` Drew Adams
2012-02-12 16:58     ` Stefan Monnier
2012-02-12 17:18       ` Drew Adams
2012-02-12 18:17         ` Stefan Monnier
2012-02-13  6:16       ` 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=F6EB9EB31449486280586DA81F239691@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=rgm@gnu.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).