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 19:38:19 +0200 Message-ID: References: <5018244D-6882-44E3-BE5A-F7ADFD68CA78@gmail.com> <4CBFE7D9.7060406@diplan.de> <8149C452-8C07-4458-AE99-73717076A134@gmail.com> <4CBFEC31.5060008@diplan.de> <4CBFFF5D.2010604@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=43124 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P8z5v-0000u4-Ir for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 13:38:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P8z5u-00065E-83 for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 13:38:27 -0400 Received: from mail-ey0-f169.google.com ([209.85.215.169]:55390) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P8z5t-00063U-VW for emacs-orgmode@gnu.org; Thu, 21 Oct 2010 13:38:26 -0400 Received: by mail-ey0-f169.google.com with SMTP id d26so263796eyd.0 for ; Thu, 21 Oct 2010 10:38:25 -0700 (PDT) In-Reply-To: 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: Greg Troxel Cc: emacs-orgmode@gnu.org, Rainer Stengele On Oct 21, 2010, at 2:41 PM, Greg Troxel wrote: > > Carsten Dominik writes: > >> On Oct 21, 2010, at 10:52 AM, Rainer Stengele wrote: >> >>> 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. >> >> I see how that makes sense. However, the other use case is this: >> >> Use #A to make something higher priority. Use #C to make it lower >> than any normal stuff. All the rest mingles in #B. >> >> So your proposal makes the assumption that any priority means more >> than no priority. > > The default aBc settings were easily understandable to me and I use > A to > mark things high and C low and leave most things in the middle. > > So maybe all that's needed is a "You might expect tasks with an > explicit > priority to all be considered higher priority than tasks without an > explicit priority, but in fact unlabeled tasks inherit the default > priority." Or maybe that's redundant. I just re-read the manual section. As far as I can see, all necessary information is there. - Carsten