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:47:10 -0700 [thread overview]
Message-ID: <87d4c8uim9.fsf@transitory.lefae.org> (raw)
In-Reply-To: 87fxh4yr93.fsf@fastmail.fm
Matthew Lundin <mdl@imapmail.org> writes:
> Hi Ross,
>
> Ross Patterson <me@rpatterson.net> writes:
>
>> Matthew Lundin <mdl@imapmail.org> 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?
>>>
>>> The following FAQs provide some tips on how to do this:
>>>
>>> - http://orgmode.org/worg/org-faq.php#limit-agenda-with-tag-filtering
>>>
>>> - http://orgmode.org/worg/org-faq.php#limit-agenda-with-category-match>
>> Sorry, should have been clearer, I want to look at my work*.org tasks in
>> the the *day/week agenda* view, not just the task listing.
>
> I'm a bit confused. One of the FAQs explains how to do precisely that
> using #+FILETAGS and tag filtering (i.e., the same solution as Bernt's
> email).
The second link results in a headline list, not an "agenda day/week"
view.
Ross
next prev parent reply other threads:[~2009-03-23 19:47 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 [this message]
2009-03-24 14:12 ` Carsten Dominik
2009-03-23 19:13 ` Bernt Hansen
2009-03-23 19:19 ` Ross Patterson
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=87d4c8uim9.fsf@transitory.lefae.org \
--to=me@rpatterson.net \
--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
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).