From: David Bremner <david@tethera.net>
To: Paul Wise <pabs3@bonedaddy.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] notmuch-mutt: replace extra command with notmuch-native thread search feature
Date: Sun, 09 Apr 2023 13:00:55 -0300 [thread overview]
Message-ID: <87wn2lf3k8.fsf@minkowski.home> (raw)
In-Reply-To: <28f564aaeee5bfe4dfd007850920eecbb19daba0.camel@bonedaddy.net>
Paul Wise <pabs3@bonedaddy.net> writes:
> So I think that it would be good if there were a library for notmuch
> query construction that would take care of all the different quoting
> levels, Message-Id munging etc. This could then get language bindings
> so that notmuch based tools and MUAs could use them for interactive
> graphical query construction. Also maybe Xapian needs or has a way to
> construct queries without serialising them to a text string and the
> notmuch query construction library I propose could base itself on that.
You might be interested in the s-expression query parser. Part of the
goal is to be less dwim/quirky than the native Xapian query parser, and
to make it easier / safer to construct notmuch queries via programs.
It doesn't do the message-id munging you mention (yet?), but quoting is
IMHO saner.
It does require an extra dependency (sfsexpr).
next prev parent reply other threads:[~2023-04-09 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 0:54 [PATCH] notmuch-mutt: replace extra command with notmuch-native thread search feature Paul Wise
2023-04-08 11:42 ` David Bremner
2023-04-09 4:38 ` Paul Wise
2023-04-09 4:41 ` [PATCH v2 1/2] notmuch-mutt: fix Xapian query construction Paul Wise
2023-04-09 4:41 ` [PATCH v2 2/2] notmuch-mutt: replace extra command with notmuch thread search feature Paul Wise
2023-05-27 17:31 ` David Bremner
2023-04-09 16:00 ` David Bremner [this message]
2023-04-10 0:48 ` [PATCH] notmuch-mutt: replace extra command with notmuch-native " Paul Wise
2023-04-10 13:04 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn2lf3k8.fsf@minkowski.home \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=pabs3@bonedaddy.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://yhetil.org/notmuch.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).