From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: bug? org does not seem to sort by prioritiy #A, #B, #C, #D Date: Thu, 21 Oct 2010 09:21:38 +0200 Message-ID: <8149C452-8C07-4458-AE99-73717076A134@gmail.com> References: <5018244D-6882-44E3-BE5A-F7ADFD68CA78@gmail.com> <4CBFE7D9.7060406@diplan.de> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=42993 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8pT6-00030w-Eb for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:21:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8pT4-0000DF-HR for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:21:44 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:43294) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8pT4-0000D9-BT for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:21:42 -0400 Received: by eya28 with SMTP id 28so1193151eya.0 for ; Thu, 21 Oct 2010 00:21:41 -0700 (PDT) In-Reply-To: <4CBFE7D9.7060406@diplan.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: Rainer Stengele Cc: emacs-orgmode@gnu.org On Oct 21, 2010, at 9:12 AM, Rainer Stengele wrote: > Am 21.10.2010 09:07, schrieb Carsten Dominik: >> >> On Oct 21, 2010, at 9:01 AM, Rainer Stengele wrote: >> >>> Hi all, >>> >>> maybe this is a bug: (Org-mode version 7.01trans (release_7.01h. >>> 605.gc540) >>> >>> Having set >>> >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> ==================================================================== >>> Org Enable Priority Commands: Hide Value Toggle on (non-nil) >>> State: STANDARD. >>> Non-nil means priority commands are active. Hide Rest >>> When nil, these commands will be disabled, so that you never >>> accidentally >>> set a priority. >>> >>> Org Highest Priority: Hide Value A >>> State: STANDARD. >>> The highest priority of TODO items. A character like ?A, ?B etc. >>> More >>> >>> Org Lowest Priority: Hide Value D >>> State: SAVED and set. >>> The lowest priority of TODO items. A character like ?A, ?B etc. >>> More >>> >>> Org Default Priority: Hide Value D >>> State: SAVED and set. >>> The default priority of TODO items. More >>> >>> resulting correctly in >>> >>> (custom-set-variables >>> ... >>> '(org-highest-priority 65) >>> '(org-default-priority 68) >>> '(org-lowest-priority 68) >>> ... >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> = >>> ==================================================================== >>> >>> the custom agenda command >>> >>> ("Tp" "all todos sorted by prio" >>> ( >>> (alltodo "all todos" )) >>> ((org-agenda-sorting-strategy '(priority-down)))) >>> >>> will sort correctly by priorities #A, #B, #C, descending, >>> but will then mix up the rest of the todos with "#D" or without >>> priority. >>> "#D" does not seem to be included in the sorting. >> >> The meaning of the default priority is that tasks without a >> priority do have >> the default priority. If you need 4 priorities all higher than >> "normal tasks", >> make E your lowest and default priority >> >> - Carsten >> > Yes, works now. A bit counterintuitive, isn't it? What would be the "intuitive" meaning of default priority then? - Carsten