From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: Samuel Loury <konubinix@gmail.com>,
emacs-orgmode@gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: Re: [BUG?] Matching tags: & operator no more implicit between tags and special property
Date: Wed, 23 Aug 2023 12:21:16 +0200 [thread overview]
Message-ID: <ef4f175b-58f3-5708-8224-ae07f0c202be@vodafonemail.de> (raw)
In-Reply-To: <87h6oq2nu1.fsf@gmail.com>
Thanks for the detailed report!
On 2023-08-23 09:57, Samuel Loury wrote:
> The following tags query used to implicitly behave as a AND
> "-tag-TODO=\"TODO\"".
> Before commit f689eb44f175fbbdc4e8ef0ad6f5201b10863438, this showed only
> "nothing", as expected.
That was my short-sighted attempt to allow for unquoted minus signs
in property names, and your query right now matches all entries having
a property "tag-TODO" different from "TODO". TBH, I didn't think
about your use case, where two negations are concatenated directly
after each other.
OTOH, the unquoting ("\\-") that has been in place before above commit
was broken, which might serve as a hint that few to none actually use
minus signs in property names, at least not in queries.
Ihor, WDYT? I can (with the necessary delay to allow for proper
testing) revert to some sort of quoting in property names which would
allow for Samuel's use case again.
next prev parent reply other threads:[~2023-08-23 10:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 7:57 [BUG?] Matching tags: & operator no more implicit between tags and special property Samuel Loury
2023-08-23 10:21 ` Jens Schmidt [this message]
2023-08-23 10:37 ` Ihor Radchenko
2023-08-23 10:31 ` Ihor Radchenko
2023-08-23 10:38 ` Jens Schmidt
2023-08-23 14:00 ` [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property] Jens Schmidt
2023-08-23 15:55 ` Jens Schmidt
2023-08-24 7:30 ` Ihor Radchenko
2023-08-24 7:32 ` Ihor Radchenko
2023-08-24 8:52 ` Jens Schmidt
2023-08-25 18:46 ` Jens Schmidt
2023-08-26 10:16 ` Ihor Radchenko
2023-08-26 11:53 ` Jens Schmidt
2023-08-26 12:00 ` Ihor Radchenko
2023-08-26 12:19 ` Jens Schmidt
2023-08-26 12:22 ` Ihor Radchenko
2023-08-26 12:54 ` Jens Schmidt
2023-08-27 7:11 ` Samuel Loury
2023-08-27 7:43 ` Ihor Radchenko
2023-09-01 16:48 ` Jens Schmidt
2023-09-01 23:59 ` Tom Gillespie
2023-09-02 0:02 ` Tom Gillespie
2023-09-02 7:10 ` Ihor Radchenko
2023-09-02 13:14 ` Redoing the current tag/property parser in a real grammar [was: Re: [RFC] Quoting property names in tag/property matches] Jens Schmidt
2023-09-03 7:04 ` Ihor Radchenko
2023-09-02 13:18 ` [RFC] Quoting property names in tag/property matches Jens Schmidt
2023-08-30 16:28 ` [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property] Jens Schmidt
2023-08-31 8:08 ` Ihor Radchenko
2023-08-31 10:24 ` Jens Schmidt
2023-09-03 6:53 ` Ihor Radchenko
2023-09-03 9:25 ` Jens Schmidt
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=ef4f175b-58f3-5708-8224-ae07f0c202be@vodafonemail.de \
--to=jschmidt4gnu@vodafonemail.de \
--cc=emacs-orgmode@gnu.org \
--cc=konubinix@gmail.com \
--cc=yantar92@posteo.net \
/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).