From: Scott Randby <srandby@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: custom-set-variables considered harmful
Date: Wed, 29 Nov 2017 14:57:26 -0500 [thread overview]
Message-ID: <5be6823b-e26e-f2b9-cdd7-d2c15b850f16@gmail.com> (raw)
In-Reply-To: <CADtN0W+ro75RTsGAA13-q=MBAg4crKF=9NmXisNLjhmw8VFYXw@mail.gmail.com>
On 11/29/2017 11:35 AM, Elias Mårtenson wrote:>
> All I'm trying to say is that we currently have two methods for setting custom
> variables:
>
> - setq - works almost all the time
> - custom-set-variable - works all the time
>
> I'm not saying that anyone should make setq not work. I'm simply suggesting that
> perhaps it's a good idea to recommend users that they use the one, simple,
> mechanism that exists and works all the time.
>
> Wouldn't that make things simpler in the long run?
My question about this is what do we do if our initialization file is broken into pieces? I use an org-mode file which I tangle to an initialization file, and I have setq in various pieces of code all over the place in the org-mode file. My understanding is that you should only use one custom-set-variables or else bad things could happen. I do not want to abandon my org-mode file. How do I keep modularization and use custom-set-variables?
Scott Randby
next prev parent reply other threads:[~2017-11-29 19:57 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
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 [this message]
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=5be6823b-e26e-f2b9-cdd7-d2c15b850f16@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-devel@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).