emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Michael Brand <michael.ch.brand@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: default PRIORITY
Date: Sun, 10 Jul 2011 13:12:18 +0200	[thread overview]
Message-ID: <CALn3zogzuVSnaEjE-U=iWY8kHUx7Wb7AfamPzCgrvJFg8aoivA@mail.gmail.com> (raw)

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

next             reply	other threads:[~2011-07-10 11:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10 11:12 Michael Brand [this message]
2011-07-23 12:31 ` default PRIORITY Michael Brand
2011-07-24 19:17   ` Bastien
2011-07-24 19:52     ` Michael Brand

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='CALn3zogzuVSnaEjE-U=iWY8kHUx7Wb7AfamPzCgrvJFg8aoivA@mail.gmail.com' \
    --to=michael.ch.brand@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

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).