From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>,
Frank Roland <frokrecik@gmail.com>
Cc: 24920@debbugs.gnu.org
Subject: bug#24920: 24.5; Error on customize-update-all
Date: Thu, 10 Nov 2016 14:59:55 -0800 (PST) [thread overview]
Message-ID: <0b68d593-eddc-4b62-b8bc-7322367aaff1@default> (raw)
In-Reply-To: <CAM-tV--gNYBHW8vWxBbz-q6NqVmhr9BbbRJiyzkdGmcL-uPHYw@mail.gmail.com>
> I guess this is either a bug in cus-edit+ (wrongly assuming any of
> customized-value, saved-value, standard-value can be `eval'ed in any
> buffer), or it's a bug in Auctex (for putting a customized-value,
> saved-value, or standard-value that can't be `eval'ed in any
> buffer).
The cus-edit+.el code for this is essentially the same as the
cus-edit.el code for commands such as `customize-rogue'. And
such commands are intended (of course) to be usable with any
buffer current.
Similarly, there is nothing in a non-interactive function such
as `custom-variable-state' that says that it should be called
only from a particular buffer or set of buffers.
It is true that such functions use `eval', and there is a risk
that the property value is a sexp whose evaluation raises an error.
Perhaps a usage note is called for in the doc of such functions?
next prev parent reply other threads:[~2016-11-10 22:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 16:52 bug#24920: 24.5; Error on customize-update-all Frank Roland
2016-11-10 19:29 ` Noam Postavsky
2016-11-10 22:59 ` Drew Adams [this message]
2016-11-10 23:59 ` npostavs
2021-09-03 9:03 ` Lars Ingebrigtsen
2022-05-02 10:12 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b68d593-eddc-4b62-b8bc-7322367aaff1@default \
--to=drew.adams@oracle.com \
--cc=24920@debbugs.gnu.org \
--cc=frokrecik@gmail.com \
--cc=npostavs@users.sourceforge.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.