From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rainer Stengele <rainer.stengele@diplan.de>
Subject: Re: bug? org does not seem to sort by prioritiy #A, #B, #C, #D
Date: Thu, 21 Oct 2010 09:12:25 +0200
Message-ID: <4CBFE7D9.7060406@diplan.de>
References: <i9oofl$sf2$1@dough.gmane.org>
	<5018244D-6882-44E3-BE5A-F7ADFD68CA78@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=48323 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P8pKK-0001OL-8f
	for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:12:41 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rainer.stengele@diplan.de>) id 1P8pKJ-0007DM-AY
	for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:12:40 -0400
Received: from ns.diplan.de ([212.34.188.4]:46317 helo=mail.diplan.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rainer.stengele@diplan.de>) id 1P8pKI-0007CD-VC
	for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 03:12:39 -0400
In-Reply-To: <5018244D-6882-44E3-BE5A-F7ADFD68CA78@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org

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?
Thanks!

- Rainer