emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neilen Marais <nmarais@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Recursive org-agenda-files
Date: Fri, 14 Oct 2011 18:53:32 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111014T204934-595@post.gmane.org> (raw)
In-Reply-To: CALRk1saG5wbxGpan-O=fy32M4HwH1_6OxfOgGSCF4RmWuCRtiQ@mail.gmail.com


Matthew Sauer <improv.philosophy <at> gmail.com> writes:

> My understanding is that you want a file that gets moved into the
> active directory to be automatically included in the agenda?
> From worg:
> You can simply include the directory (as one of the items) in the
> value of the variable org-agenda-files:
> (setq org-agenda-files '("/my/special/path/org/active/"))

Thanks for the suggestion. Tried it already and found that it is unfortunately 
not recursive. I tend to make directories with projects under the active 
directory, then put the org file and supporting files in the directory. E.g.



What's nice about this is that my project notes, todos and support files are 
close to each other. Also, I can simply use the dired listing of the active dir 
as my "active projects list" in GTD parlance :)
>  Not that playing with agenda hooks might have some advantages.

I have indeed cooked up a hooky solution that should have hit the list by the 
time you read this :)


  reply	other threads:[~2011-10-14 18:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 15:48 Recursive org-agenda-files Neilen Marais
2011-10-03 17:38 ` netty hacky
2011-10-04  7:19   ` Neilen Marais
2011-10-04  7:32     ` Jambunathan K
2011-10-04  7:54       ` Jambunathan K
2011-10-04 12:42         ` Neilen Marais
2011-10-04 14:12           ` Nick Dokos
2011-10-05  2:33             ` Matthew Sauer
2011-10-14 18:53               ` Neilen Marais [this message]
2011-10-14 18:48             ` Neilen Marais
  -- strict thread matches above, loose matches on Subject: below --
2008-10-31 12:30 Sullivan, Gregory (US SSA)
2008-10-31 14:32 ` mclundin

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=loom.20111014T204934-595@post.gmane.org \
    --to=nmarais@gmail.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).