notmuch/doc/man7, branch 0.35_rc0thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.35_rc02022-01-29T20:37:59Zdoc: replace :math: for subscripts in notmuch-sexp-queries(7)2022-01-29T20:37:59ZDavid Bremnerdavid@tethera.net2022-01-26T13:30:45Zurn:sha1:5c183d814b2cb3155cb8eec1c8ab44868ff75d30
Sphinx pulls in mathjax to do :math:, which complicates viewing the
html version offline. The direct :sub: is supported directly in html.
rename built_with.sexpr_query to built_with.sexp_queries2021-12-04T00:06:06ZDavid Bremnerdavid@tethera.net2021-10-30T18:49:20Zurn:sha1:b264a49be3dccb7d110eae6420019a052f1f665b
It is confusing to use two different names (sexp vs sexpr) when
compared with the command line option --query=sexp and (furthermore)
singular vs plural when compared with the man page title.
doc/sexp-queries: replace definition lists with block quotes.2021-10-25T11:25:35ZDavid Bremnerdavid@tethera.net2021-10-11T12:56:15Zurn:sha1:93104f0d9de4fa2919896a55dfdd207bbaf22589
This document contains meaningful markup in the terms, which makeinfo
complains about. Replace the use of definition lists with regular
paragraphs containing quote blocks. This is accomplished by splitting
the "term" from the definition with a blank line.
doc: remove explicit formatting of terms in definition lists2021-10-25T11:25:22ZDavid Bremnerdavid@tethera.net2021-10-11T12:56:14Zurn:sha1:00fdf10937a3ef0292424fb67208b74c753b35fd
Sphinx-doc already formats the terms appropriately for a given
backend (bold in html and man). `makeinfo` complains noisily about
formatting inside a @item if we add our own explicit formatting.
This change may change the formatting in the info output. On the other
hand, the existing use of quotes for bold is not that great anyway.
In some places blank lines were removed to preserve the logical
structure of a definition list.
doc/sexp-queries: update synopsis and description2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:45Zurn:sha1:49aa44bb012e8c2412b5447119b78b61842740b8
I chose to go with a somewhat terse synopsis to try to keep the length
of the page down.
lib/parse-sexp: apply macros2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:41Zurn:sha1:551254eb76c9bb558078f04f21df1f6089cb03d6
Macros implement lazy evaluation and lexical scope. The former is
needed to make certain natural constructs work sensibly (e.g. (tag
,param)) but the latter is mainly future-proofing in case the DSL is
is extended to allow local bindings.
For technical background, see chapters 6 and 17 of [1] (or some other
intermediate programming languages textbook).
[1] http://cs.brown.edu/courses/cs173/2012/book/
lib/parse-sexp: handle saved queries2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:37Zurn:sha1:6ab2d9b1a2e62b76960df8e80ff2a45d9c6a8551
This provides functionality analogous to query: in the Xapian
QueryParser based parser. Perhaps counterintuitively, the saved
queries currently have to be in the original query syntax (i.e. not
s-expressions).
lib/parse-sexp: parse user headers2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:35Zurn:sha1:a07ef8abf5248c1128ddc75b8139ae807a88abd9
One subtle aspect is the replacement of _find_prefix with
_notmuch_database_prefix, which understands user headers. Otherwise
the code mainly consists of creating a fake prefix record (since the
user prefixes are not in the prefix table) and error handling.
lib/parse-sexp: support infix subqueries2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:34Zurn:sha1:cc5992a30470222791c24849da04a3c0403ecce5
This is necessary so that programs can take infix syntax queries from
a user and use the sexp query syntax to construct e.g. a refinement of
that query.
lib/parse-sexp: expand queries2021-09-05T00:07:19ZDavid Bremnerdavid@tethera.net2021-08-24T15:17:33Zurn:sha1:afe85e65786df1df9abf261393b4b4e6e2e86009
The code here is just gluing together _notmuch_query_expand with the
existing sexp parser infrastructure.