| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
In certain conditions the parallel calls to sphinx-build could
collide, yielding a crash like
Exception occurred:
File "/usr/lib/python3/dist-packages/sphinx/environment.py", line 1261, in get_doctree
doctree = pickle.load(f)
EOFError: Ran out of input
|
|
I can't figure out how checking the sign of a bool ever worked. The
following program demonstrates the problem (i.e. for me it prints 1).
#include <stdio.h>
#include <stdbool.h>
int main(int argc, char **argv) {
bool x;
x = -1;
printf("x = %d\n", x);
}
This seems to be mandated by the C99 standard 6.3.1.2.
|
|
Because the string_map functions are not exported, we test via message
properties.
|
|
|
|
|
|
|
|
Indent the directive properly to attach it to Threads autoclass
documentation.
Fixes:
WARNING: don't know which module to import for autodocumenting
'__str__' (try placing a "module" or "currentmodule" directive in the
document, or giving an explicit module name)
|
|
Fix documentation build sphinx warning:
filesystem.rst:18: WARNING: Title underline too short.
|
|
The simplistic mocking in conf.py falls short on python 3.7. Just use
unittest.mock instead.
Fixes:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 368, in eval_config_file
execfile_(filename, namespace)
File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 150, in execfile_
exec_(code, _globals)
File "/path/to/notmuch/bindings/python/docs/source/conf.py", line 39, in <module>
from notmuch import __VERSION__,__AUTHOR__
File "/path/to/notmuch/bindings/python/notmuch/__init__.py", line 54, in <module>
from .database import Database
File "/path/to/notmuch/bindings/python/notmuch/database.py", line 25, in <module>
from .globals import (
File "/path/to/notmuch/bindings/python/notmuch/globals.py", line 48, in <module>
class NotmuchDatabaseS(Structure):
TypeError: __mro_entries__ must return a tuple
|
|
When invoking gpg as a backgrounded tool, it's important to let gpg
know that it is backgrounded, to avoid spurious prompts or other
breakage.
In particular, https://bugs.debian.org/913614 was a regression in
GnuPG which causes problems when importing keys without a terminal,
but gpg expects one.
Ensuring that notmuch-emacs always invokes gpg as a background process
should avoid some of these unnecessary failure.
Thanks to Justus Winter for finding this problem.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
|
|
|
|
|
|
|
|
|
|
This should no longer be needed on the official debian autobuilders,
but it might help others with merged /usr build environments.
|
|
bash, in it's wisdom, sets that variable when invoked as /bin/sh, but
then doesn't act as bash, at least not to the degree we need to run
scripts.
|
|
Joerg Jaspert [1] reported problems with evince reading unsuffixed
temporary files in Debian.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920856
|
|
Yes, a build chroot can have /usr/bin/bash, thanks to usrmerge, but we
can't depend on it existing in the user's system.
|
|
|
|
|
|
This is based on my subjective assessment of what is user/packager
facing and important from the output of 'git shortlog'
|
|
|
|
Just a stub for now.
|
|
|
|
This ${prefix}/share/vendor-completion convention seems to be debian
specific, so leave the global default alone for now.
|
|
This adds completion files for zsh that cover most of notmuch's cli.
The files in completion/zsh are formatted so that they can be found by
zsh's completion system if put $fpath. They are also registered to the
notmuch-* pattern, so they can be called externally using _dispatch.
Update installation recipe and drop debian/notmuch.examples to avoid
breakage. This means zsh completion is not installed for debian, to be
fixed in a future commit.
Amended by db: use regexp searching for address completion. This seems
to be fast enough to work without a cache.
|
|
Previously any hook functions attached to `notmuch-mua-send-hook' were
ignored.
|
|
|
|
|
|
|
|
The immediate motivation is to have dh_installman look in debian/tmp
|
|
The main goal here is to be able to install the notmuch-mutt script
with an absolute shebang. I have tried to make the notmuch-mutt
Makefile use configure information from notmuch if available, but make
suitable guesses if not.
|
|
This can be used to set shebang lines during install.
|
|
Follow distro-centric rules to reduce the chance of surprising
behaviour due to PATH changes
|
|
This can be used to set shebang lines during install.
|
|
Normally we'd mark it broken, but perversely missing regexp support
actually makes the test pass.
|
|
Currently these tests just fail when notmuch is built against Xapian
1.2.x
|
|
Unfortunately 514fb397c9 somewhat messed up the "debian-snapshot"
target, by including .git in the generated tarball.
|
|
notmuch release 0.27-3 for unstable (sid) [dgit]
[dgit distro=debian]
|
|
This hangs up dgit. It's probably not useful for users of the source
package to have debian/.gitignore, but it should not hurt.
|
|
|
|
If the database path specified in the configuration file does *not*
start with a /, presume that it is relative to $HOME and modify the
path used to open the database accordingly.
|
|
[dgit --overwrite]
|
|
In current Debian sid / testing, emacs25 is a transitional package,
and emacs-gtk, emacs-lucid, and emacs-nox are the real packages.
Emacs 23 is not available in emacs after oldoldstable.
|
|
We should probably not git://, and it needs a branch to not confuse
e.g. vcswatch.
|
|
As reported by Sean Whitton, there are mailers (in particular the
Debian Bug Tracking System) that have sensible In-Reply-To headers,
but un-useful-for-notmuch References (in particular with the BTS, the
oldest reference is last). I looked at a sample of about 200K
messages, and only about 0.5% these had something other than a single
message-id in In-Reply-To. On this basis, if we see a single
message-id in In-Reply-To, consider that as authoritative.
|
|
The idea is that if a message-id parses with this function, the MUA
generating it was probably sane, and in particular it's probably safe
to use the result as a parent from In-Reply-to.
|
