emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ross Patterson <me@rpatterson.net>
To: emacs-orgmode@gnu.org
Subject: Re: Restrict agenda view to multiple files matching a pattern?
Date: Mon, 23 Mar 2009 12:19:39 -0700	[thread overview]
Message-ID: <87ljqwujw4.fsf@transitory.lefae.org> (raw)
In-Reply-To: 87vdq0t5mf.fsf@gollum.intra.norang.ca

Bernt Hansen <bernt@norang.ca> writes:

> Ross Patterson <me@rpatterson.net> writes:
>> So far at least, I have my tasks broken up into multiple *.org files
>> whose names reflect general categories.  Often I want to look at the
>> agenda view for files starting with "work" to look at all my work
>> tasks.
>> Is there a way I can do this or a better way I should be organizing my
>> tasks?  Putting all my tasks into one work file would just be way too
>> much as I am a freelancer and have a lot to keep track of.  Similarly I
>> don't really want to tag every work task just to support this.  Any
>> suggestions?
> Hi Ross,
> For my setup I have multiple files that are work related.  Everything in
> the file is work related (or not).  I put a #+FILETAGS: entry at the top
> which tags all tasks for work - then I can limit the agenda to WORK
> tasks easily.
> ,----[ norang.org ]
> `----
> I'm currently filtering stuff I'm supposed to do @Work with my @Work
> tag.  There are other tags in the file (like NORANG above) that allows
> me to limit it specifically to a single client etc.
> Then I added a entry for @Work to org-tag-alist using 'W' so I can
> filter by this tag easily.
> Does that help?

Excellent!  Yes it does?


      reply	other threads:[~2009-03-23 19:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 18:56 Restrict agenda view to multiple files matching a pattern? Ross Patterson
2009-03-23 19:08 ` Matthew Lundin
2009-03-23 19:08 ` Matthew Lundin
2009-03-23 19:13   ` Ross Patterson
2009-03-23 19:27     ` Matthew Lundin
2009-03-23 19:47       ` Ross Patterson
2009-03-24 14:12         ` Carsten Dominik
2009-03-23 19:13 ` Bernt Hansen
2009-03-23 19:19   ` Ross Patterson [this message]

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=87ljqwujw4.fsf@transitory.lefae.org \
    --to=me@rpatterson.net \
    --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).