From: Rainer Stengele <rainer.stengele@diplan.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug? org does not seem to sort by prioritiy #A, #B, #C, #D
Date: Thu, 21 Oct 2010 10:52:45 +0200 [thread overview]
Message-ID: <4CBFFF5D.2010604@diplan.de> (raw)
In-Reply-To: <C4CE9C04-8CEF-469D-8553-0D3CF234783D@gmail.com>
Am 21.10.2010 09:39, schrieb Carsten Dominik:
>
> On Oct 21, 2010, at 9:30 AM, Rainer Stengele wrote:
>
>> Am 21.10.2010 09:21, schrieb Carsten Dominik:
>>>
>>> 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
>> Well, I would have expected that if I define a priority #D as lowest priority it is not excluded from sorting.
>
>
> It *is* included in the sorting. All #D's come after the #A's, #B's, and #C's. Only that "all #D's" includes all entries that have no specified priority. Within each main priority, the precise order of the entries is determined by other
> factors well, like if it is a deadline or an overdue scheduled item..... That make the D's look random and the other not - but the same is going on everywhere.
>
> You can look at the computed priority (which is used for sorting) by pressing (I think) "P" on every item.
>
> Would you like to make a proposal for a paragraph in the manual to clarify this? Or are you proposing to change how this works?
>
>
>
> - Carsten
>
My guessing is that a naive user (like me ...) does expect any defined priority (like #D in this case) to have a higher priority than a "non" priority item.
If more users see it this way I would propose a change, if not I would suggest a short hint in the manual.
- Rainer
next prev parent reply other threads:[~2010-10-21 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 7:01 bug? org does not seem to sort by prioritiy #A,#B,#C,#D Rainer Stengele
2010-10-21 7:07 ` bug? org does not seem to sort by prioritiy #A, #B, #C, #D Carsten Dominik
2010-10-21 7:12 ` Rainer Stengele
2010-10-21 7:21 ` Carsten Dominik
2010-10-21 7:30 ` Rainer Stengele
2010-10-21 7:39 ` Carsten Dominik
2010-10-21 8:52 ` Rainer Stengele [this message]
2010-10-21 9:01 ` Carsten Dominik
2010-10-21 9:38 ` Rainer Stengele
2010-10-21 18:07 ` Samuel Wales
2010-10-21 20:26 ` Carsten Dominik
2010-10-21 12:41 ` Greg Troxel
2010-10-21 17:38 ` Carsten Dominik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CBFFF5D.2010604@diplan.de \
--to=rainer.stengele@diplan.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).