From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: default PRIORITY Date: Sun, 10 Jul 2011 13:12:18 +0200 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38312) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qfrvx-00083l-Pa for emacs-orgmode@gnu.org; Sun, 10 Jul 2011 07:12:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qfrvw-0000cT-6s for emacs-orgmode@gnu.org; Sun, 10 Jul 2011 07:12:21 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:37101) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qfrvv-0000cL-Ry for emacs-orgmode@gnu.org; Sun, 10 Jul 2011 07:12:20 -0400 Received: by wyg36 with SMTP id 36so2524394wyg.0 for ; Sun, 10 Jul 2011 04:12:18 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode Hi all It seems to me that there is an inconsistency with the default PRIORITY in searches and custom agenda blocks of types like "tags" or "tags-todo". Assume org-default-priority B and an agenda file #+begin_src org ,* TODO [#C] low prio ,* TODO default prio ,* TODO [#A] high prio #+end_src When org-agenda-custom-commands contains #+begin_src emacs-lisp ("x" "test" ((tags-todo "PRIORITY<=\"C\""))) #+end_src the agenda block looks like this: TODO [#A] high prio TODO default prio TODO [#C] low prio This is like expected: The item without PRIORITY gets the default B for sorting from org-get-priority called in org-scan-tags. When org-agenda-custom-commands contains #+begin_src emacs-lisp ("x" "test" ((tags-todo "PRIORITY=\"B\""))) #+end_src the agenda block is empty. I expected that the item without PRIORITY matches and is shown because I expect it to get the default B also when matching. But this is not the case for org-cached-entry-get called in org-scan-tags at "(eval matching)". Even worse: The item without PRIORITY is shown with "PRIORITY<\"B\"". During debugging it seemed to me that this is simply because the item gets the PRIORITY " " when matching. Now I am not sure whether I would be able to provide a patch and how this should be solved: Only in org-scan-tags or better in org-entry-properties and/or friends like org-entry-get, org-cached-entry-get and maybe more? Tested with current release_7.5-416-g27360b1 and Emacs 23.3.1 Michael