From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darlan Cavalcante Moreira Subject: Re: (Possible Feature Request) Hiding Tags in Agenda View/Implementing Contexts in Org Date: Thu, 08 Oct 2009 15:56:15 -0300 Message-ID: <4ace35d5.0d84100a.3c78.4394@mx.google.com> References: <330fb75e0910062216t7244cc75k91ea51d1cc45e279@mail.gmail.com> <4ACE0E39.4080908@os.inf.tu-dresden.de> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MvyOb-00043O-RC for emacs-orgmode@gnu.org; Thu, 08 Oct 2009 15:11:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MvyOV-00040J-Uf for emacs-orgmode@gnu.org; Thu, 08 Oct 2009 15:11:25 -0400 Received: from [199.232.76.173] (port=42722 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MvyOV-00040D-KE for emacs-orgmode@gnu.org; Thu, 08 Oct 2009 15:11:19 -0400 Received: from mail-ew0-f228.google.com ([209.85.219.228]:49162) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MvyA7-0005yr-6Z for emacs-orgmode@gnu.org; Thu, 08 Oct 2009 14:56:27 -0400 Received: by ewy28 with SMTP id 28so11651041ewy.42 for ; Thu, 08 Oct 2009 11:56:22 -0700 (PDT) In-Reply-To: <4ACE0E39.4080908@os.inf.tu-dresden.de> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Martin Pohlack Cc: emacs-orgmode@gnu.org 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 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