From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: Re: A simpler remember architecture Date: Wed, 07 Oct 2009 08:17:16 +0100 Message-ID: <87hbub1xmr.wl%ucecesf@ucl.ac.uk> References: <20524da70909291348m6e1a6611ve01d6dac2faca93c@mail.gmail.com> <2647742D-5A30-4F33-8FDF-E5203B2E0246@gmail.com> <4AC472F7.4020208@online.de> <87r5tnyn18.fsf@gollum.intra.norang.ca> <871vlgep0m.fsf@gollum.intra.norang.ca> Reply-To: e.fraga@ucl.ac.uk Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MvQmA-00018K-Mc for emacs-orgmode@gnu.org; Wed, 07 Oct 2009 03:17:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MvQm6-000145-CN for emacs-orgmode@gnu.org; Wed, 07 Oct 2009 03:17:30 -0400 Received: from [199.232.76.173] (port=48814 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MvQm6-00013r-3r for emacs-orgmode@gnu.org; Wed, 07 Oct 2009 03:17:26 -0400 Received: from mx20.gnu.org ([199.232.41.8]:13153) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MvQm5-0003nE-NA for emacs-orgmode@gnu.org; Wed, 07 Oct 2009 03:17:25 -0400 Received: from vscane-c.ucl.ac.uk ([144.82.108.43]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MvQm0-0007iA-D4 for emacs-orgmode@gnu.org; Wed, 07 Oct 2009 03:17:20 -0400 In-Reply-To: From: Eric S Fraga 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: Daniel Clemente Cc: org-mode At Tue, 6 Oct 2009 16:33:08 +0200, Daniel Clemente wrote: > > > > > To cater more to the OP's needs, consider using a special tag for such > > common tasks, like :COMMON: > > > > The create a special agenda view hat just shows this tag. > > > This is a very nice solution. I thought of the agenda view as a way > to view your agenda, but now I see that it can actually serve as a > generic task dispatcher. Yes, it took me a while of using agenda purely as a list of my tasks before I realised (thanks to this list) that it was ever so powerful! I use the tag :clocked: for all my clockable activities (which are not that many, maybe 8 or so). What I found particularly useful was to set the org-tags-exclude-from-inheritance variable to include :clocked: so that you can have as complex a hierarchy below any clockable item without it appearing in the agenda. eric