From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Piotr Zielinski" Subject: Re: How to sort by tags Date: Mon, 28 Aug 2006 15:59:19 +0100 Message-ID: <3c12eb8d0608280759t4876cfedr89a4ef7c8c63babd@mail.gmail.com> References: <4858.1156758160@lap1.smtl.co.uk> <7d78ec8e3164d4af4193e4d6de0b5086@science.uva.nl> <12881.1156768572@lap1.smtl.co.uk> <07fa357d0c6e333ad111b87cdf25a818@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GHiaA-0002WG-GF for emacs-orgmode@gnu.org; Mon, 28 Aug 2006 10:59:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GHia9-0002VV-Ge for emacs-orgmode@gnu.org; Mon, 28 Aug 2006 10:59:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GHia8-0002VQ-NA for emacs-orgmode@gnu.org; Mon, 28 Aug 2006 10:59:20 -0400 Received: from [64.233.184.239] (helo=wr-out-0506.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GHij6-0000sX-Qe for emacs-orgmode@gnu.org; Mon, 28 Aug 2006 11:08:36 -0400 Received: by wr-out-0506.google.com with SMTP id 71so385064wra for ; Mon, 28 Aug 2006 07:59:19 -0700 (PDT) In-Reply-To: <07fa357d0c6e333ad111b87cdf25a818@science.uva.nl> Content-Disposition: inline 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: Carsten Dominik Cc: emacs-orgmode@gnu.org On 28/08/06, Carsten Dominik wrote: > Yes, with tags as context this would make sense...... > > Other input, anyone? Sorting by tags might be thought of as a special case of multi-block agenda buffer, in which you can execute multiple agenda commands without erasing the buffer. For example, you can use org-agenda first to list all the items tagged "work" and then all the items tagged "home". The only change in the current implementation would be not to erase the agenda buffer. This approach would require one org buffer scan for each keyword, which might be inefficient. The advantage of this approach is that it leaves it up to the user how do deal with multi-tagged entries. If an element tagged ":work:home:" should appear under both "work" and "home", then the user would specify the block list to be '("work" "home"). If such elements should appear only in "work", the specification would be ("work" "+work-home"). Alternatively, we can put elements ":work:home:" into a separate list by specifying three lists ("+work-home" "+home-work" "+work+home"). In general, without prior knowledge about the semantics of tags, choosing one of those approaches automatically will be difficult. Finally, having the whole power of the org-agenda and tag matching, one could construct more sophisticated blocks, for example, consisting of all ":work:" entries that are TODO at the same time. Piotr