From: Samuel Loury <konubinix@gmail.com>
To: Jens Schmidt <jschmidt4gnu@vodafonemail.de>,
Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [RFC] Quoting property names in tag/property matches [Was: [BUG?] Matching tags: & operator no more implicit between tags and special property]
Date: Sun, 27 Aug 2023 09:11:57 +0200 [thread overview]
Message-ID: <878r9xez7m.fsf@gmail.com> (raw)
In-Reply-To: <a11fc399-4082-e2de-8046-e289cc467b7c@vodafonemail.de>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
I have a dumb question.
IIUC, it needs a lot of effort to deal with implicit & correctly. I
initially used it because de manual said it was ok, but I would have
used explicit & if the manual had said so.
I wonder if we could just stop saying that & is optional and have a
simpler parsing.
IMHO, "-tag&-todo=TODO" is totally ok. I even imagine we could say that
& and | are forbidden to say anything else than AND and OR and people
would be ok with that.
IOW, I wonder of the time and effort to deal with optional & is worth
it. WDYT?
--
Konubinix
GPG Key : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE 5C36 75D2 3CED 7439 106A
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2023-08-27 7:13 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
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 [this message]
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=878r9xez7m.fsf@gmail.com \
--to=konubinix@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--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).