From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Interpretation of priorities in org-mode Date: Thu, 9 Aug 2007 07:05:41 +0200 Message-ID: <0f0cabd3a5a978dc3ee6cc84a831b2cc@science.uva.nl> References: <4916e1b50708010747n49b65809p7c94f7d8c804962f@mail.gmail.com> <3c12eb8d0708010813i1b6c0fb5p90ba4f5ff6886326@mail.gmail.com> <874pjjxkn4.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IJ0DT-0004lg-Rw for emacs-orgmode@gnu.org; Thu, 09 Aug 2007 01:05:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IJ0DP-0004jr-Al for emacs-orgmode@gnu.org; Thu, 09 Aug 2007 01:05:46 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IJ0DP-0004jo-5u for emacs-orgmode@gnu.org; Thu, 09 Aug 2007 01:05:43 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IJ0DO-0003Rq-Mj for emacs-orgmode@gnu.org; Thu, 09 Aug 2007 01:05:42 -0400 In-Reply-To: <874pjjxkn4.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org On Aug 1, 2007, at 18:52, Bastien wrote: > "Piotr Zielinski" writes: > >> The reason why I decided to use priorities was because it was easier >> to make them work with org-agenda. In particular, I don't know how to >> make the agenda display, for example, "all headlines without >> the :today: tag in the order of increasing deadlines". If this is >> possible, I'll happily switch to tags. > > This search should be achieved with a custom command like: > > (setq org-agenda-custom-commands > '(("u" tags "-today" > ((org-agenda-sorting-strategy '(time-up)))))) > > See (info "(org)Setting Options") ... but i can't have the '(time-up) > option to be taken into account. At least it works for selecting all > but the :today: tag. The reason why this does not work is that sorting by time only works if the entry has been *selected* for inclusion into the agenda by a timestamp. If it was selected, for example, by tag, the it would be unclear which time to use, there might be many in the entry, like scheduled, deadline, or a plain time stamp marking this also as an appointment. - Carsten