From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: org-agenda queries for absent properties
Date: Sun, 30 Jul 2023 19:13:38 +0200 [thread overview]
Message-ID: <9132e58f-d89e-f7df-bbe4-43d53a2367d2@vodafonemail.de> (raw)
The following was initially meant as bug report until I understood that
it's actually some sort of feature ...
Consider the following todo list:
-------------------- todos.org --------------------
* TODO relax
* TODO do this
:PROPERTIES:
:patchday: 202302
:END:
* TODO do that
:PROPERTIES:
:patchday: 202305
:END:
* TODO work harder
:PROPERTIES:
:patchday: 202308
:END:
-------------------- todos.org --------------------
When I use an agenda query
patchday>=202305
on that I get the result:
Headlines with TAGS match: patchday>=202305
Press ‘C-u r’ to search again
todos: TODO do that
todos: TODO work harder
However for the following:
patchday<=202305
I get
Headlines with TAGS match: patchday<=202305
Press ‘C-u r’ to search again
todos: TODO relax
todos: TODO do this
todos: TODO do that
since the absent property "patchday" on the "relax" todo entry is
defaulted to value zero, obviously.
So I would like to have something easier to type (and remember! why not
"!=" or "/="?) then
patchday<>0&patchday<=202305
How about starred agenda property operators that match only if the
operand property is actually present, which would result in this query:
patchday<=*202305
Section <info:org#Matching tags and properties> does not seem to provide
any information on "definedness" expressions for properties.
Thanks.
next reply other threads:[~2023-07-30 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 17:13 Jens Schmidt [this message]
2023-07-31 6:45 ` org-agenda queries for absent properties Ihor Radchenko
2023-08-01 18:50 ` Jens Schmidt
2023-08-02 6:45 ` Ihor Radchenko
2023-08-05 10:56 ` Jens Schmidt
2023-08-06 7:55 ` Ihor Radchenko
2023-08-06 9:19 ` Jens Schmidt
2023-08-06 14:42 ` Jens Schmidt
2023-08-07 11:53 ` Ihor Radchenko
2023-08-07 20:20 ` Jens Schmidt
2023-08-08 7:04 ` Ihor Radchenko
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=9132e58f-d89e-f7df-bbe4-43d53a2367d2@vodafonemail.de \
--to=jschmidt4gnu@vodafonemail.de \
--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).