Re: bug? org does not seem to sort by prioritiy #A, #B, #C, #D

[Rainer Stengele <rainer.stengele@diplan.de>]

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