From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 11565@debbugs.gnu.org
Subject: bug#11565: delayed init variables don't get documentation properties
Date: Mon, 28 May 2012 15:53:29 -0400 [thread overview]
Message-ID: <874nr09j5y.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvsjel7pdm.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 27 May 2012 09:00:03 -0400")
Stefan Monnier wrote:
>> I guess either we undo 3), or change 2) so that it sets the variable to
>> nil. The latter seems ok to me ...?
>
> Undoing the var-part of 3 sounds fine to me.
There's a downside to doing that, in that bug#11036 will be reopened.
What's the downside to making custom-initialize-delay temporarily bind
variables to nil?
Another option: Snarf-documentation to check if variables are bound, or
members of custom-delayed-init-variables.
next prev parent reply other threads:[~2012-05-28 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 22:29 bug#11565: delayed init variables don't get documentation properties Glenn Morris
2012-05-27 13:00 ` Stefan Monnier
2012-05-28 19:53 ` Glenn Morris [this message]
2012-05-28 19:56 ` Glenn Morris
2012-05-28 20:27 ` Stefan Monnier
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=874nr09j5y.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11565@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).