From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 9712@debbugs.gnu.org
Subject: bug#9712: 24.0.50; doc about byte-compiling `defcustom'
Date: Tue, 11 Oct 2011 01:09:37 -0400 [thread overview]
Message-ID: <jwvsjn0yv3l.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <7D2DB4482840400D81CC74F60D0091DC@us.oracle.com> (Drew Adams's message of "Mon, 10 Oct 2011 21:51:00 -0700")
>> The bug is not in the doc but in the behavior.
> That was my feeling, as well. But I did not expect agreement, based on the
> commented code.
> The bug has been there for multiple major Emacs releases now -
> a decade or so, and appears to have been introduced intentionally.
> If there is no plan to fix it soon, perhaps the info that is in the
> comments should at least be conveyed to users.
The introduction of lexical-binding makes this issue more serious
because this code does not obey the lexical-binding variable (and
escapes the sanity checks of cconv.el, hence occasionally hiding
problems when converting to lexical-binding).
> Alternatively, the code could be uncommented and byte-compiling be let free to
> do what is advertised that it does. The downside would be showing users the
> constant values in Customize, but that seems like less of a disfunction than
> what we have now.
We need to solve the display issue some other way, yes.
Stefan
next prev parent reply other threads:[~2011-10-11 5:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-09 20:42 bug#9712: 24.0.50; doc about byte-compiling `defcustom' Drew Adams
2011-10-10 13:27 ` Drew Adams
2011-10-10 15:53 ` Drew Adams
2011-10-10 22:38 ` Drew Adams
2011-10-11 2:17 ` Stefan Monnier
2011-10-11 4:51 ` Drew Adams
2011-10-11 5:09 ` Stefan Monnier [this message]
2011-10-11 5:40 ` Drew Adams
2011-10-11 12:48 ` Stefan Monnier
2011-10-11 14:35 ` 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=jwvsjn0yv3l.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9712@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).