emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Daniel Clemente <n142857@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Switching between many contexts
Date: Mon, 02 Mar 2009 13:31:28 -0500	[thread overview]
Message-ID: <87zlg3rd33.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87ocwjzts2.fsf@CPU107.opentrends.net> (Daniel Clemente's message of "Mon\, 02 Mar 2009 19\:03\:41 +0100")

Hi Daniel,

<Quoted text wrapped>

Daniel Clemente <n142857@gmail.com> writes:

>   Hi. I have this scenario: I track several projects in a single file,
>   each in its own level-1 section, but each week I'm working only on
>   one project.  In my agenda (C-a a) I'm currently seeing scheduled
>   tasks from all projects, and I would like to exclude all projects
>   but one.  I recently added a CATEGORY property to each section.
>
>
>   My questions are:
>
> 1. How can I exclude a category from the agenda view?  Probably with
> key \ TAB CATEGORY="something", but I can't make it work and I'm
> confused by the many types of searches that are referred to in the
> manual.

I use tags instead of categories for filtering.  Categories for me are
only displayed in the agenda as extra information for what the task
belongs to.

Since tags are inherited you can just add a tag to the level 1 task and
then filter using that tag.

> >
> 2. How can I create an agenda view that looks like the normal agenda,
> but ignores some categories? (at least on that file).

Using tags instead of categories:

Do a normal agenda view and then limit with / TAB tag-names-goes-here or
use one of your fast key selections for tags.  (/ key)

You can use a filter to remove tasks with a specific tag

C-c a t / - TAB PROJ1 RET

will display all TODO tasks and then remove any tasks with the PROJ1
tag.  You can repeat the /- TAB tagname sequence to remove multiple
projects.

For my standard tags I have quick keys defined in my org-tag-alist so I
can just use those to filter tasks.  That works great!

> >
> 3. Do you implement this scenario in other ways? For instance, one can
> add the COMMENT keyword the unwanted projects, use different files,
> close all old tasks after each context switch, use other tags, …

I split projects into separate files and add a #+FILETAGS: at the top.
For instance my org.org file has
#+FILETAGS: ORG

and all tasks in that file get the ORG tag.

For clients I create one or more files and use a FILETAGS setting to
create a tag for that client - then I can limit the agenda to just that
client quickly.  Some clients have multiple project files (one of my
clients has client systems which I work on so each system has its own
org file but I can view everything for that client by limiting to the
client tag)

I find limiting the agenda with tag filters very quick and effective.

HTH,
Bernt

  parent reply	other threads:[~2009-03-02 18:31 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
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 ` Bernt Hansen [this message]
2009-03-02 21:47 ` Switching between many contexts Matthew Lundin

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=87zlg3rd33.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=n142857@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).