emacs-orgmode
[Top][All Lists]
Advanced

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

[Orgmode] Re: Problem with agenda file list


From: Jose A. Ortega Ruiz
Subject: [Orgmode] Re: Problem with agenda file list
Date: Sun, 27 Apr 2008 22:11:51 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

Hi Carsten,

Carsten Dominik <address@hidden> writes:

> Hi Jose,
>
> in principle it would be possible, of course, to write a
> custom function that directly modifies a special Org
> configuration file.  However, that is even less clean than
> what I was doing so far and is bound to cause problems.  What
> if another person does *not* have a special file for Org?
> Should I then directly manipulate .emacs?  I think this is
> not acceptable.
>

I think we're misunderstanding each other :) What i really want is to
just set in my .emacs something along the lines of

  (setq org-agenda-files '("/home/jao/org/a.org" "home/jao/org/b.org"))
  (require 'org-install)

and be sure that org won't write any custom-set-variables or
custome-set-faces in my custom file. Last time i tried doing that,
org-agenda-files appeared automagically in my custom-set-variables
section, together with a face definition for font-lock-warning in my
custom-set-faces... they were put in my .emacs, but i was using a
separate custom-file, so i just set and loaded custom-file before
loading org, and then org-agenda-files and font-lock-warning are written
by org in my custom-file instead of .emacs. But since i'm setting
org-agenda-files in my .emacs, what i'd like is that it wouldn't appear
in custom-set-variables.

My understanding was that, in order to prevent this behaviour (that is,
the automatic modification of custom-set-variables and -faces), my only
option was to use the org files list file. Am i confused?

Thanks!
jao

> There is of course, a simple solution for you:  Set the value
> of org-agenda-files with a lisp setq form in .emacs, and never use
> `C-c [' and `C-c ]' to modify the list.  If you want to be sure,
> disable these functions with `disable-command'.
>






reply via email to

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