From: Robert Weiner <rsw@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Philippe Vaucher" <philippe.vaucher@gmail.com>,
"Elias Mårtenson" <lokedhs@gmail.com>,
"Stefan Monnier" <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: custom-set-variables considered harmful
Date: Fri, 1 Dec 2017 15:42:13 -0500 [thread overview]
Message-ID: <CA+OMD9hYbP+CHk60tyojs446CAsWuN5bOWwr78B3SsgAvLhvAw@mail.gmail.com> (raw)
In-Reply-To: <8782ed42-3aec-4111-b4f0-471c838e7370@default>
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
On Wed, Nov 29, 2017 at 10:03 AM, Drew Adams <drew.adams@oracle.com> wrote:
>
> Here's a crazy possibility (not a suggestion, but maybe
> food for thought): Make `setq' do `customize-set-variable'
> for an option and do what it does now otherwise.
>
I have been wondering about this too. Are there any arguments for not
having setq run the setter of a custom option when available? Is it a
performance issue?
Is it a load ordering issue?
If there is no fundamental issue, then this would be great because one
wouldn't have to worry about the type of a variable when setting it.
Bob
[-- Attachment #2: Type: text/html, Size: 1653 bytes --]
next prev parent reply other threads:[~2017-12-01 20:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 17:10 custom-set-variables considered harmful Stefan Monnier
2017-11-06 9:02 ` Philippe Vaucher
2017-11-06 12:19 ` Clément Pit-Claudel
2017-11-06 16:36 ` raman
2017-11-07 19:53 ` Stefan Monnier
2017-11-08 10:06 ` Vivek Dasmohapatra
2017-11-08 13:38 ` Stefan Monnier
2017-11-08 14:23 ` Vivek Dasmohapatra
2017-11-08 15:17 ` Stefan Monnier
2017-11-08 15:34 ` Vivek Dasmohapatra
2017-11-13 16:26 ` Stefan Monnier
2017-11-24 7:04 ` Elias Mårtenson
2017-11-24 7:16 ` Stefan Monnier
2017-11-24 17:37 ` Clément Pit-Claudel
2017-11-24 17:56 ` Stefan Monnier
2017-11-26 12:15 ` Elias Mårtenson
2017-11-26 16:30 ` Drew Adams
2017-11-28 14:12 ` Philippe Vaucher
2017-11-28 16:50 ` John Wiegley
2017-12-01 9:44 ` Philippe Vaucher
2017-11-29 3:36 ` Elias Mårtenson
2017-11-29 15:00 ` Stefan Monnier
2017-11-29 15:03 ` Drew Adams
2017-12-01 20:42 ` Robert Weiner [this message]
2017-12-02 0:10 ` Richard Stallman
2017-12-02 1:58 ` Drew Adams
2017-12-02 5:56 ` Teemu Likonen
2017-11-29 16:35 ` Elias Mårtenson
2017-11-29 19:57 ` Scott Randby
2017-11-29 22:08 ` Stefan Monnier
2017-11-30 0:40 ` Scott Randby
2017-12-01 9:51 ` Philippe Vaucher
2017-12-04 13:48 ` Stefan Monnier
2017-12-04 15:36 ` Eli Zaretskii
2017-12-04 16:05 ` Robert Weiner
2017-12-04 23:50 ` Richard Stallman
2017-12-05 1:45 ` Stefan Monnier
2017-11-23 20:12 ` John Wiegley
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=CA+OMD9hYbP+CHk60tyojs446CAsWuN5bOWwr78B3SsgAvLhvAw@mail.gmail.com \
--to=rsw@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=lokedhs@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=philippe.vaucher@gmail.com \
--cc=rswgnu@gmail.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).