emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matthew Lundin <mdl@imapmail.org>
To: Eraldo Helal <admin@eraldo.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Handling org-file agenda dependenncies?
Date: Sat, 28 Mar 2009 06:55:53 -0500	[thread overview]
Message-ID: <m2tz5doo8m.fsf@fastmail.fm> (raw)
In-Reply-To: <loom.20090328T105651-742@post.gmane.org> (Eraldo Helal's message of "Sat\, 28 Mar 2009 11\:07\:00 +0000 \(UTC\)")

Hi Eraldo,

Eraldo Helal <admin@eraldo.at> writes:

> Mike Newman <mike <at> newmanfamily.me.uk> writes:
>  
>> When you use the standard commands to add/removes files from the
>> agenda, it will write a definition for the variable org-agenda-files to
>> the custom section of your .emacs file.
>
> That would still mean removing every org-file in the tree manually
> when wanting to make a project "inactive".
>
>> If you want to deal with trees of files, you might be better off
>> removing the variable from the custom section, defining it
>> yourself and updating it manually.
>
> The questions here is... How could one define it?

I think you could set something like the following in your .emacs file:

--8<---------------cut here---------------start------------->8---
(load-library "find-lisp")
(setq org-agenda-files (append (find-lisp-find-files "~/directory1" "\.org$")
			       (find-lisp-find-files "~/directory2" "\.org$")         
                               (find-lisp-find-files "~/directory3" "\.org$")))
--8<---------------cut here---------------end--------------->8---

This will search the directories above recursively for org files.
Whenever you want to remove a project from your agenda, simply delete
the appropriate line and evaluate the expression. I'd imagine someone
else can think of a way to do this more economically, though.

Best,
Matt

next prev parent reply	other threads:[~2009-03-28 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  0:31 Handling org-file agenda dependenncies? Eraldo Helal
2009-03-27 21:46 ` Mike Newman
2009-03-28 11:07   ` Eraldo Helal
2009-03-28 11:55     ` Matthew Lundin [this message]
2009-03-30  7:54   ` 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

  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=m2tz5doo8m.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=admin@eraldo.at \
    --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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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