From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with agenda file list
Date: Sat, 26 Apr 2008 13:06:57 +0200 [thread overview]
Message-ID: <yr0gr6csub72.fsf@google.com> (raw)
In-Reply-To: 87fxt9ux7n.fsf@cantor.griswold.home
Dan Griswold <dgriswol@rochester.rr.com> writes:
> Hello all,
>
> I've encountered a strange problem with the org-agenda-files
> variable.
>
> When I start up org-mode (which I do from my .emacs) the following
> unsavory events happen:
>
> 1. org-agenda-files is set to only the first file in the list;
> 2. custom-set-variables is set to just org-agenda-files (blowing
> away all other customizations);
> 3. custom-set-variables and custom-set-faces are written to .emacs,
> even if custom-file is set to a different file name (as in my
> setup).
>
I've encountered problems 2) and 3). The latter can be fixed by loading
custom-file before org, and i had to explicitly set the value of
org-agenda-files in custom-set-variables to get the value i want.
I put all my customizations in separate files and rarely use
custom-set-{variables, faces}. It'd be nice if org offered the option of
*not* writing any customization back (i was specially puzzled by its
overwriting some of my faces, which i manage using color-theme) and be
totally customizable using elisp outside the customize interface. That's
already almost the case: all may other elisp settings for org work
nicely. IMHO, custom-set-{variables, faces} should be modified only
when *explicitly* requested by the user, either by using customize or
manually editing custom-file.
Cheers,
jao
--
"When you come to a fork in the road, take it"
-Yogi Berra, baseball coach.
next prev parent reply other threads:[~2008-04-26 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 3:11 Problem with agenda file list Dan Griswold
2008-04-26 11:06 ` Jose A. Ortega Ruiz [this message]
2008-04-26 11:28 ` Dan Griswold
2008-04-26 20:25 ` Carsten Dominik
2008-04-27 15:17 ` Eddward DeVilla
2008-04-27 15:51 ` Carsten Dominik
2008-04-27 17:08 ` Jose A. Ortega Ruiz
2008-04-27 18:44 ` Carsten Dominik
2008-04-27 20:11 ` Jose A. Ortega Ruiz
2008-04-28 4:12 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yr0gr6csub72.fsf@google.com \
--to=jao@gnu.org \
--cc=emacs-orgmode@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.