emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mike Newman <mike@newmanfamily.me.uk>
To: emacs-orgmode@gnu.org
Subject: Re: Handling org-file agenda dependenncies?
Date: Fri, 27 Mar 2009 21:46:55 +0000	[thread overview]
Message-ID: <20090327214655.56888aaf@newmanfamily.me.uk> (raw)
In-Reply-To: <938fae2d0903261731p5bbc84e5v12f63e136f868474@mail.gmail.com>

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.

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.

I would find it useful to be able to switch to an "*Org Agenda Files
Buffer*", edit this and save it to update - but I don't suppose anyone 
would think it worth the effort of coding.

As an interesting aside - if in Dired I rename a file that I am
currently visiting, the buffer's name will be changed automatically.
However, org-agenda-files will not be updated in this case.

On Fri, 27 Mar 2009 01:31:19 +0100
Eraldo Helal <office@eraldo.at> wrote:

> I have projects with non-text files.
> Many of them having sub-,subsub-projects etc. (nested)
> Therefore I made directories for them using the project
> name. /<project
> name>/<subproject name>/etc
> Each having it's own <(sub-)project name>.org file in it.
> My question:
> How can I add|remove a whole project from the agenda?
> e.g. If I remove project1.org file from the agenda...
>      /project1/subprojectX.org would still be in there!
> Or is there a way to assign and then set a group of org.files to
> inactive(=remove from agenda)?
> Any other suggestions|methods for solving this problem?

  reply	other threads:[~2009-03-27 21:47 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 [this message]
2009-03-28 11:07   ` Eraldo Helal
2009-03-28 11:55     ` Matthew Lundin
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:

  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=20090327214655.56888aaf@newmanfamily.me.uk \
    --to=mike@newmanfamily.me.uk \
    --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).