If you have an org file for work stuff and another one for home stuff, each one
with their respective filetags, then IMHO it is better simply not to set the
@work and @home tags explicitly. If something is work related then refile it to
the work org file instead of setting the @work tag. You lose flexibility, but
avoid this problem.
Darlan
At Thu, 08 Oct 2009 18:07:21 +0200,
Martin Pohlack <m...@os.inf.tu-dresden.de> wrote:
>
> Hi Migual, all,
>
> Miguel Fernando Cabrera wrote:
> […]
> > I have several files, gtd.org (I put the name after a tutorial, but I
> > don't implement pure gtd) and home.org. One if for work related tasks
> > and the other for personal projects and task that are usually
> > performed at home.
>
> I use a very similar setup as you do, one file for work, one for home.
> I tagged the topmost hierarchy in each file with a corresponding tag
> (:@work:, :@home:) and use inheritance for context propagation.
>
> I also use distinct agenda views for home and work stuff.
>
> ("w" "Agenda and work items at work"
> ((agenda "" ((org-agenda-ndays 1)
> (org-agenda-prefix-format "%?-12t% s")
> (org-agenda-files (quote ("~/Daten/plan_work.org")))
> (org-agenda-skip-function
> (quote (org-agenda-skip-entry-if (quote regexp) "maybe")))))
> (todo "INBOX"
> ((org-agenda-skip-function
> (quote (org-agenda-skip-entry-if (quote scheduled))))
> (org-agenda-files (quote ("~/Daten/plan_work.org")))))
> (stuck "" ((org-agenda-files (quote ("~/Daten/plan_work.org")))))
> (alltodo "" ((org-agenda-skip-function
> (quote (org-agenda-skip-entry-if
> (quote notregexp) "^\\*+ \\(TICKLER\\|WAITING\\)"
> (quote regexp) "^\\*+ NEXT .*:ag_"
> (quote scheduled))))
> (org-agenda-overriding-header
> "Buggy items (missing schedule / agenda):")
> (org-agenda-files (quote ("~/Daten/plan_work.org")))))
> (tags "{^ag_.*}-{^ag_.*_\\(meeting\\|call\\)$}-maybe"
> ((org-agenda-sorting-strategy (quote (tag-up)))
> (org-agenda-skip-function
> (quote
> (org-agenda-skip-subtree-if
> (quote regexp)
> "^\\*+ \\(DONE\\|CANCELED\\|CONTAINER\\|PROJECT\\|MAYBE\\) ")))
> (org-agenda-overriding-header "Agendas (non-regular):")
> (org-agenda-files (quote ("~/Daten/plan_work.org")))))
> (tags
> "LEVEL>1...@work-maybe-todo=\"MAYBE\"-TODO=\"DONE\"-TODO=\"CANCELED\"-TODO=\"PROJECT\"-TODO=\"CONTAINER\"-TODO=\"\""
> ((org-agenda-skip-function (quote (org-agenda-skip-entry-if
> (quote scheduled)))))))
> ((org-agenda-prefix-format "")))
>
>
> […]
>
> > Now, to really do what I want would be cool to have a way of saying to
> > org that don't show the "@work" tag.
>
> This sounds like an intriguing feature to me. For my setup, I
> sometimes have each tag twice in each agenda line as refiling inlines
> inherited tags.
>
> In my work agenda I have many lines similar to this one:
>
> In 1 d.: TODO task A :@work::@work:
>
> So the @work context is there *three* times on screen:
> * from the whole agenda title,
> * directly as tag in the task, and
> * inherited in the task.
>
> So I have two partially orthogonal feature requests here.
> * Could we show tags only once, for example, for cases where a task
> has a tag directly and if it has inherited it?
> * Could we have a filter for not showing certain tags in agenda views
> at all, for example, if the tag information would be redundant due
> to information provided by the whole agenda (work agenda -> don't
> show :@work:).
>
> Note that I cannot easily disable tag inheritance in my setup as I use
> it also for propagating the :maybe: tag to descendants of projects.
>
> Cheers,
> Martin Pohlack
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
