From: Nick Dokos <nicholas.dokos@hp.com>
To: Neilen Marais <nmarais@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Recursive org-agenda-files
Date: Tue, 04 Oct 2011 10:12:14 -0400 [thread overview]
Message-ID: <21575.1317737534@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Neilen Marais <nmarais@gmail.com> of "Tue, 04 Oct 2011 12:42:59 -0000." <loom.20111004T143930-712@post.gmane.org>
Neilen Marais <nmarais@gmail.com> wrote:
> Jambunatha,
>
>
> > > Have you considered adding it to say org-mode-hook?
> >
> > Seems like a Wrong suggestion to me.
> >
> > Try using `C-c [' to add the current org file. I am assuming that org
> > files are created by hand and not by some daemon that spits out agenda
> > files when you are away from emacs.
>
> Not a daemon, no, but I do tend to move files around. I.e. I'll move a project
> file/dir from my "someday" folder to my "active" folder. I would like to avoid
> any further manual steps to get it integrated in my agenda.
>
> Is there a hook function that gets called every time an agenda view is opened or
> refreshed? I could probably use that to update the agenda list.
>
Seek and ye shall find:
C-h v org-agenda--hook RET
will list all the matching hooks. Which one to choose? I'll leave that up
to the interested reader :-) Or try
C-h v org--hook RET
to get a list of *all* the org hooks.
Nick
next prev parent reply other threads:[~2011-10-04 14:12 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 [this message]
2011-10-05 2:33 ` Matthew Sauer
2011-10-14 18:53 ` Neilen Marais
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:
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=21575.1317737534@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=nmarais@gmail.com \
/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 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).