From: Daniel Clemente <email@example.com>
To: Bernt Hansen <firstname.lastname@example.org>
Cc: org-mode mailing list <email@example.com>
Subject: Re: Switching between many contexts
Date: Tue, 03 Mar 2009 12:27:43 +0100 [thread overview]
Message-ID: <87zlg27snk.fsf@CPU107.opentrends.net> (raw)
In-Reply-To: <firstname.lastname@example.org> (Bernt Hansen's message of "Mon, 02 Mar 2009 13:34:35 -0500")
> Assign a FLUFF tag to your tasks then run the agenda normally and remove
> the fluff with
> / - TAB FLUFF RET
Thanks, this works. I will use tags instead of categories.
> or if you do that often set up org-tags-alist with F for FLUFF and just
> / - F
In fact I would like to use often the agenda view with several tags excluded, so the ideal setup would be an agenda custom search.
But I don't know which command to use in org-agenda-custom-commands: I don't want tags-todo (that's a heading list), but the real agenda (with its colors, dates, deadlines, etc.). However, the search type called „agenda“ seems not to accept tags to search.
Maybe „agenda“ could accept tags to search?
Or else I can try to do a custom command which emulates the agenda but adds this filter; maybe with a local variable or with „skip conditions“ (org-agenda-skip-function).
next prev parent reply other threads:[~2009-03-03 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 18:03 Daniel Clemente
2009-03-02 18:21 ` Samuel Wales
2009-03-02 18:34 ` Bernt Hansen
2009-03-03 11:27 ` Daniel Clemente [this message]
2009-03-03 13:05 ` Matthew Lundin
2009-03-03 13:31 ` Carsten Dominik
2009-03-03 6:20 ` Manuel Hermenegildo
2009-03-04 6:17 ` Carsten Dominik
2009-03-04 10:01 ` Daniel Clemente
2009-03-05 18:41 ` Auto-saving/loading files (without prompts) David Thole
2009-03-06 15:21 ` Jason F. McBrayer
2009-03-02 18:31 ` Switching between many contexts Bernt Hansen
2009-03-02 21:47 ` Matthew Lundin
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 \
* 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).