emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: emacs-orgmode@gnu.org
Subject: Re: Minor gotcha with org-agenda-files
Date: Sat, 22 Jan 2011 11:41:45 -0600	[thread overview]
Message-ID: <m2lj2cltt2.fsf@verilab.com> (raw)
In-Reply-To: AANLkTi=nxm8aXc54xJfUsu23xvgPanNwhWcV_WvWpdDP@mail.gmail.com

suvayu ali <fatkasuvayu+linux@gmail.com> writes:

> On Sat, Jan 22, 2011 at 5:31 PM, Tommy Kelly <tommy.kelly@verilab.com> wrote:
>> I just figured out why, despite having a setq in my .emacs, my
>> org-agenda-files wasn't what I thought it should be.
>> It's because if you modify that variable using C-c [ or C-c ], then any
>> explicit setq is rendered obsolete by the custom-set-variables
>> entry that gets added automatically.
> This is nothing org specific. Its how customise works. This is the
> reason people are encouraged to _not_ mix customise with setq. I for
> example use customise for everything except org settings.

Ah but hang on.

First, is it reasonable to consider it obvious (I mean, it wasn't to me)
that using C-c [ invokes customize?

Second, even if it is reasonable, isn't it the case that customize
offers a temporary change of variables? You have to explicitly ask it to
make the change permanent, no?

Overall, it just caught me unawares that C-c [ should write something in
one of my files without even telling me let alone asking me. Maybe it's
just me though. 


  reply	other threads:[~2011-01-22 17:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 16:31 Minor gotcha with org-agenda-files Tommy Kelly
2011-01-22 16:49 ` suvayu ali
2011-01-22 17:41   ` Tommy Kelly [this message]
2011-01-22 19:59     ` Eric S Fraga
2011-01-23  8:15       ` suvayu ali
2011-01-23 10:06         ` Eric S Fraga
2011-01-23 10:53           ` Carsten Dominik
2011-01-23 13:56             ` Bernt Hansen
2011-01-22 16:32 Tommy Kelly

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2lj2cltt2.fsf@verilab.com \
    --to=tommy.kelly@verilab.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).