unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mauricio <briqueabraque@yahoo.com>
To: help-gnu-emacs@gnu.org
Cc: help-gnu-emacs@gnu.org
Subject: Re: Replacing custom-set-variables
Date: Mon, 15 Sep 2008 11:06:39 -0300	[thread overview]
Message-ID: <48CE6BEF.9080305@yahoo.com> (raw)
In-Reply-To: <87vdwzcq0e.fsf@lion.rapttech.com.au>

>>
>> In .emacs I have a few variables defined using:
>>
>> (custom-set-variables
>>  '(var1 val1)
>>  '(var2 val2)
>>  '(var3 val3))
>>
>> How can I define those same variables in .emacs
>> without using custom-set-variables?
>>
> 
> Just use setq e.g.
> 
> (setq var1 value1)
> 
> but don't forget to also remove the corresponding bits in the custom
> section. 
> 
> but can I ask why you want to do this? 
> 
> For a long time, I stuck to using the older (setq ....) method, but now
> I've switched to using customize whenever possible. I've noticed that
> some 'odd' behavior I used to get with the older traditional method have
> gone away now that I'm using customize as much as possible. I do still
> have some stuff to convert over and plan to do so one day when I get the
> motivation.....
> 
> In particular, I noticed some inconsistent behavior between some
> packages that supported customize when I also configured them 'manually'
> (and without corresponding settings in the customize section). for some
> reason, the default customize setting would override my setq setting. I
> never investigated very closely, but suspect it was related to how the
> initialization of the custom variables was handled. the quick and easy
> solution was to just set the values via customize and remove my hand
> crafted version. 
> 
> I've also found using customize is also useful in alerting you to
> changes in packages after an upgrade - something you generally don't get
> using the older manual approach. 
> 
> Tim
> 

Based on all comments, maybe a begginer like
me would prefer custom-set-... until I learn
more about a few emacs details, specially
regarding to how modes deal with variables.

Best,
Maurício





  reply	other threads:[~2008-09-15 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.19185.1221326409.18990.help-gnu-emacs@gnu.org>
2008-09-13 18:08 ` Replacing custom-set-variables Joost Diepenmaat
2008-09-13 19:05 ` Andy Stewart
2008-09-13 20:13 ` Giorgos Keramidas
2008-09-14  4:33   ` Tim X
2008-09-14  8:39     ` rustom
2008-09-14 21:30     ` Nikolaj Schumacher
2008-09-14  4:25 ` Tim X
2008-09-15 14:06   ` Mauricio [this message]
2008-09-13 17:19 Mauricio
2008-09-13 22:20 ` Drew Adams
2008-09-14  0:17   ` Lennart Borgman (gmail)
2008-09-14  0:53     ` 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=48CE6BEF.9080305@yahoo.com \
    --to=briqueabraque@yahoo.com \
    --cc=help-gnu-emacs@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.
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).