<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/doc, branch debian/bullseye</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fbullseye</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=debian%2Fbullseye'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2021-02-18T11:55:28Z</updated>
<entry>
<title>doc: bump copyright year</title>
<updated>2021-02-18T11:55:28Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-02-18T11:52:39Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=346b999ae6f1af6a8dbe7ef960c15adf18e6a15c'/>
<id>urn:sha1:346b999ae6f1af6a8dbe7ef960c15adf18e6a15c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>build/docs: move docstring prereq to file targets</title>
<updated>2020-12-10T01:55:38Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-12-10T01:55:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ed7ca948ae31ac0e1d3633a2f58fb3e4aecd03de'/>
<id>urn:sha1:ed7ca948ae31ac0e1d3633a2f58fb3e4aecd03de</id>
<content type='text'>
Under a sufficiently high level of parallelism [1] there seems to be a
a race condition that allows sphinx-build to start running before the
docstrings are extracted. This change moves the docstring stamp from
the phony targets sphinx-html and sphinx-info to the file targets that
they depend on. I'm not sure why this makes things better, but I am
fairly confident it does not make things worse, and experimentally it
seems to eliminate the race condition.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976934
</content>
</entry>
<entry>
<title>Rename version to version.txt</title>
<updated>2020-10-30T19:14:24Z</updated>
<author>
<name>Ralph Seichter</name>
<email>github@seichter.de</email>
</author>
<published>2020-10-28T14:44:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=981d5a01689937ba45f3cd9dbdcdc65e6d264286'/>
<id>urn:sha1:981d5a01689937ba45f3cd9dbdcdc65e6d264286</id>
<content type='text'>
Building Notmuch on macOS is known to cause problems because the Notmuch
distribution archive contains two files named "version". These names
clash with the &lt;version&gt; header as defined in C++20. Therefore, the
existing naming will likely become a problem on other platforms as well,
once compilers adopt the new standard.

Signed-off-by: Ralph Seichter &lt;github@seichter.de&gt;
Amended-by: db s/keyword/header/ in commit message.
</content>
</entry>
<entry>
<title>emacs: Use makefile-gmake-mode in Makefile*s</title>
<updated>2020-08-10T00:14:36Z</updated>
<author>
<name>Jonas Bernoulli</name>
<email>jonas@bernoul.li</email>
</author>
<published>2020-08-08T11:49:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=c4541353765dec837c1c2f912b1bf6661827429c'/>
<id>urn:sha1:c4541353765dec837c1c2f912b1bf6661827429c</id>
<content type='text'>
Use `makefile-gmake-mode' instead of `makefile-mode' because the
former also highlights ifdef et al. while the latter does not.

"./Makefile.global" and one "Makefile.local" failed to specify any
major mode at all but doing so is necessary because Emacs does not
automatically figure out that these are Makefiles (of any flavor).
</content>
</entry>
<entry>
<title>doc: add new python bindings to main documentation tree.</title>
<updated>2020-07-15T11:37:11Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-07-11T13:20:27Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a05da45523a8ce65a2db73040824bb7307e7351d'/>
<id>urn:sha1:a05da45523a8ce65a2db73040824bb7307e7351d</id>
<content type='text'>
A separate conf.py and doc directory (or will be needed if someone wants
to build the bindings docs separately from notmuch.
</content>
</entry>
<entry>
<title>doc: replace use of environment variables with a generated config</title>
<updated>2020-07-15T11:32:15Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-07-11T13:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0e03e2d45e36edb635229f356bf41f153c30a70f'/>
<id>urn:sha1:0e03e2d45e36edb635229f356bf41f153c30a70f</id>
<content type='text'>
It is getting unwieldy to pass configuration options on the
sphinx-build command line, and I anticipate further use of
conditionals.

As far as I could tell, execing a string is the idiomatic way to
emulate include in Python.
</content>
</entry>
<entry>
<title>doc: make gzipped man pages reproducible</title>
<updated>2020-07-11T16:57:17Z</updated>
<author>
<name>Jonas Witschel</name>
<email>diabonas@archlinux.org</email>
</author>
<published>2020-07-11T16:04:35Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=a962842d9b0b43b7d218860b196eecd5ef666088'/>
<id>urn:sha1:a962842d9b0b43b7d218860b196eecd5ef666088</id>
<content type='text'>
gzip includes the name of the uncompressed file and its modification
timestamp into the compressed archive. The latter makes it hard to
reproduce the generated files bit for bit at a later time, so omit this
information from the archive using the "--no-name" option. This is a
reproducibility best practice, see
https://wiki.debian.org/ReproducibleBuilds/TimestampsInGzipHeaders
</content>
</entry>
<entry>
<title>doc: field processor support now always included, adjust manual pages</title>
<updated>2020-06-06T10:54:34Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2020-06-02T20:21:59Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=507d2f07a6c74eea86f87b637d0b67a0ddc1fc81'/>
<id>urn:sha1:507d2f07a6c74eea86f87b637d0b67a0ddc1fc81</id>
<content type='text'>
The features that require field processor support, are now just
documented w/o mentioning **Xapian Field Processors**' is needed
for those.

Replaced "compact" and "field_processor" with "retry_lock" in
build_with config option, as it is currently the only one that
is optionally excluded. The former 2 are now documented as
features always included.

Dropped one 'we' "passive" in notmuch-search-terms.rst. It was the
only one, and inconsistent with rest of the documentation in that
file.

Dropped message about conditional open-ended ranges support, as
those are now always supported.
</content>
</entry>
<entry>
<title>bump date in documentation</title>
<updated>2020-06-01T23:58:52Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-06-01T23:58:52Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=01fe987eec29b13f69309fa09730b6f8fc796c4a'/>
<id>urn:sha1:01fe987eec29b13f69309fa09730b6f8fc796c4a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: fix for out-of-tree builds of notmuch-emacs docs</title>
<updated>2020-06-01T12:07:50Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2020-05-31T16:15:03Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ee8dba1c3013a00c0d1185583ea084f8ce3699b7'/>
<id>urn:sha1:ee8dba1c3013a00c0d1185583ea084f8ce3699b7</id>
<content type='text'>
The sphinx-doc include directive does not have the ability to include
files from the build tree, so we replace the include with reading the
files in conf.py. The non-trivial downside of this is that the emacs
docstrings are now defined for every rst source file. They are
namespaced with docstring::, so hopefully there will not be any
surprises. One thing that is noticable is a small (absolute) time
penalty in running sphinx-doc.
</content>
</entry>
</feed>
