[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: custom-set-variables considered harmful

From: Scott Randby
Subject: Re: custom-set-variables considered harmful
Date: Wed, 29 Nov 2017 14:57:26 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]