On Wed, Jun 17 2020, Tomi Ollila wrote:
> On Wed, Jun 17 2020, Dan Čermák wrote:
>
>>
>> I have tried updating the package in openSUSE Tumbleweed to 0.30~rc2 but
>> running the tests results in the following failures:
>> --8<---cut here-
On Wed, Jun 17 2020, Dan Čermák wrote:
>
> I have tried updating the package in openSUSE Tumbleweed to 0.30~rc2 but
> running the tests results in the following failures:
> --8<---cut here---start->8---
> T357-index-decryption: Testing indexing decrypted mail
>
On Mon, Jun 15 2020, David Bremner wrote:
> Floris Bruynooghe writes:
>
>> [testenv]
>> deps =
>> @@ -14,3 +14,6 @@ commands = pytest --cov={envsitepackagesdir}/notmuch2
>> {posargs}
>>
>> [testenv:pypy35]
>> basepython = pypy3.5
>> +
>> +[testenv:pypy36]
>> +basepython = pypy3.6
>
> I'm
Hi Anton,
On Thu, May 21 2020, Anton Khirnov wrote:
> ping
Great (an important) stuff in this series !
...just that...
Floris did good review on your changes the next day.
What I remember was there (looked 30 mins ago)
- style: somewhat important (I press more there). Easy to get better,
Checking existence of pyconfig.h to determine whether CFFI-based
notmuch bindings are buildable is not enough; for example Fedora 32
ships pyconfig.h in python3-libs package, but python3-devel is required
to be installed for the bindings to build.
Executing cffi.FFI().verify() is pretty close to
On Sun, Jun 07 2020, David Bremner wrote:
> Tomi Ollila writes:
>>
>> +Dependencies
>> +
>> +
>> +Support for Xapian 1.2 is removed. The minimum supported version of
>> +Xapian is now 1.4
Checking existence of pyconfig.h to determine whether CFFI-based
notmuch bindings are buildable is not enough; for example Fedora 32
ships pyconfig.h in python3-libs package, but python3-devel is required
to be installed for the bindings to build.
Executing cffi.FFI().verify() is pretty close to
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index 1921127fe02c..a16689cae04a 100644
--- a/NEWS
+++ b/NEWS
@@ -36,6 +36,12 @@ Introduce new CFFI-based python bindings in the python
module named
"notmuch2". Officially deprecate (but still support) the older
Also tell users what the consequences of a "No" answer is when
python version is less than 3.5, cffi or setuptools is missing,
or no pytest >= 3.0 is available.
---
configure | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index
On Fri, Jun 05 2020, David Bremner wrote:
> As an initial heuristic, report anyone with at least 15 lines of code
> in the current source tree. Test corpora are excluded, although
> probabably this doesn't change much about the list of authors
> produced.
> ---
> devel/author-scan.sh | 11
On Fri, Jun 05 2020, David Bremner wrote:
> See id:m27dwp40sx@guru.guru-group.fi
LGTM.
Tomi
> ---
> this is on top of Tomi's NEWS patch re Xapian
> NEWS | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/NEWS b/NEWS
> index a16689ca..556172bb 100644
>
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index 1921127fe02c..a16689cae04a 100644
--- a/NEWS
+++ b/NEWS
@@ -36,6 +36,12 @@ Introduce new CFFI-based python bindings in the python
module named
"notmuch2". Officially deprecate (but still support) the older
On Wed, Jun 03 2020, David Bremner wrote:
> As an initial heuristic, report anyone with at least 15 lines of code
> in the current source tree. Test corpora are excluded, although
> probabably this doesn't change much about the list of authors
> produced.
> ---
>
> I realized both AUTHORS and
post-push comments =D
On Mon, Jun 01 2020, Daniel Kahn Gillmor wrote:
> Signed-off-by: Daniel Kahn Gillmor
> ---
> NEWS | 35 +++
> 1 file changed, 35 insertions(+)
>
> diff --git a/NEWS b/NEWS
> index 14db7f6f..1921127f 100644
> --- a/NEWS
> +++ b/NEWS
> @@
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
The notmuch2 CFFI-based Python interface is not buildable unless
python3 dev package and python3 setuptools are installed.
Check that these exist in configure (and disable notmuch2 bindings
build if not) so that build of these bindings don't fail when make(1)
is executed.
---
configure | 16
On Sat, Apr 25 2020, William Casarin wrote:
> This implements the notmuch-tree version of notmuch-show-filter-thread
> and binds it to the L key.
No reasoning in commit message why 'L' is chosen...
Tomi
>
> Signed-off-by: William Casarin
> ---
> emacs/notmuch-tree.el | 9 +
> 1 file
On Sun, May 31 2020, David Bremner wrote:
> 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
On Mon, May 25 2020, Floris Bruynooghe wrote:
> In tox.ini the earliest version is 3.5 and if memory serves me right
> there's a reasonably good reason for that. I think the notmuch2
> bindings use some features not yet present in 3.4. But anything >= 3.5
> should be supported and if not a bug.
On Sat, Apr 25 2020, Jonas Bernoulli wrote:
> As recommended by the byte-compiler.
I don't know about v3 2/3, but this, v3 3/3 looks good to me.
Tomi
> ---
> test/emacs-attachment-warnings.el | 23 +++
> 1 file changed, 11 insertions(+), 12 deletions(-)
>
> diff --git
Fixed emacs docstrings to be consistent. No functional change.
- removed some (accidental) indentation
- removed some trailing newlines
- added trailing periods where missing (some exclusions)
---
V2 of id:"20200503212136.11070-1-tomi.oll...@iki.fi"
changes to v1:
- trailing periods removed
On Thu, May 21 2020, Daniel Kahn Gillmor wrote:
> In out-of-tree builds, $TEST_DIRECTORY doesn't contain
> json_check_nodes.py. This caused 27 tests to fail in such an
> environment.
are you shure the run_emacs.sh change in
id:"20200423212643.864-1-tomi.oll...@iki.fi"
is not needed ? =D
On Thu, May 21 2020, Daniel Kahn Gillmor wrote:
> On Mon 2020-05-04 00:21:36 +0300, Tomi Ollila wrote:
>> Fixed emacs docstrings to be consistent. No functional change.
>>
>> - removed some (accidental) indentation
>> - removed some trailing newlines
>> - add
On Thu, May 21 2020, Daniel Kahn Gillmor wrote:
> On Thu 2020-05-21 00:16:48 +0300, Tomi Ollila wrote:
>> (just tested this latest works)
>
> Thanks for looking into this, Tomi!
>
> Do you have a patch to propose?
Looked a bit (now). Somewhat complicated to make perfect (
On Thu, May 21 2020, Tomi Ollila wrote:
>
> the message that prints FIXED, does not execute print_test_description
> but the ones that do BROKEN or FAIL does (did not fully check but yes).
>
> And:
>
> print_test_description ()
> {
> test -z "$test_
On Tue, May 12 2020, Daniel Kahn Gillmor wrote:
> I'm debugging/diagnosing/trying to clean up some "FIXED" known-broken
> tests right now.
>
> Sometimes, depending on circumstances i can't predict (race
> conditions?), I see funny output like:
>
> ~~~
> Use "make V=1" to see the details for
get nice, clean, useable and maintainable solution.
Tomi
>
> JV
>
>
> Tomi Ollila writes:
>
>>
>> Did you have spec in mind ? =D
>>
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
On Tue, May 12 2020, Jörg Volbers wrote:
>> My gut reaction is that doing more formatting in notmuch reply
>> is probably a mistake; it's hard enough to get two users to
>> agree on these kind of customizations, never mind two different
>> MUAs. Probably what we need to do is make sure the
On Fri, May 08 2020, Daniel Kahn Gillmor wrote:
> Several functions in test/test-lib.sh used variable names that are
> also used outside of those functions (e.g. $output and $expected are
> used in many of the test scripts), but they are not expected to
> communicate via those variables.
>
> We
On Wed, May 06 2020, Daniel Kahn Gillmor wrote:
> When checking cryptographic signatures, Notmuch relies on GMime to
> tell it whether the certificate that signs a message has a valid User
> ID or not.
>
> If the User ID is not valid, then notmuch does not report the signer's
> User ID to the
On Wed, May 06 2020, Daniel Kahn Gillmor wrote:
> Several functions in test/test-lib.sh used variable names that are
> also used outside of those functions (e.g. $output and $expected are
> used in many of the test scripts), but they are not expected to
> communicate via those variables.
>
> We
On Mon, May 04 2020, Daniel Kahn Gillmor wrote:
> Hi Tomi--
>
> On Sat 2020-05-02 00:15:57 +0300, Tomi Ollila wrote:
>> I did not see anything suspicious in code, but
>>
>> I got these test failures:
>>
>> in ubuntu 19.10 native environment, and
>&g
On Mon, May 04 2020, David Bremner wrote:
> In id:1588595993-ner-8.651@TPL520 Franz Fellner reported that tags
> starting with 'attachment' are removed by 'notmuch reindex'. This is
> probably related to the use of STRNCMP_LITERAL in
Haa, I looked this briefly but failed to see it is
Fixed emacs docstrings to be consistent. No functional change.
- removed some (accidental) indentation
- removed some trailing newlines
- added trailing periods where missing (some exclusions)
---
emacs/notmuch-address.el | 21 -
emacs/notmuch-draft.el | 8 ++--
On Thu, Apr 30 2020, Daniel Kahn Gillmor wrote:
> This series applies after the "Add tests for S/MIME PKCS#7 messages"
> series, which was introduced in
> id:20200428185723.660184-1-...@fifthhorseman.net
>
> With this series applied, notmuch handles standard PKCS#7 S/MIME
> messages (using
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> GPGME has a strange failure mode when it is in offline mode, and/or
> when certificates don't have any CRLs: in particular, it refuses to
> accept the validity of any certificate other than a "root" cert.
>
> This can be worked around by setting
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> This is taken from the same Internet Draft that test/smime/ca.crt
> comes from. See that draft for more details.
> https://www.ietf.org/id/draft-dkg-lamps-samples-02.html#name-pkcs12-object-for-bob
>
> We don't use it yet, but it will be used to
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
> Without this fix, we couldn't run both add_gnupg_home and
> add_gpgsm_home in the same test script.
>
> Signed-off-by: Daniel Kahn Gillmor
> ---
> test/test-lib.sh | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
On Tue, Apr 28 2020, Daniel Kahn Gillmor wrote:
>
> One final way we could normalize everything and make it less
> idiosyncratic, with shorter, simpler man pages: deprecate and then drop
> the --booloption/--no-booloption mechanisms, requiring --booloption=true
> or --booloption=false instead.
On Mon, Apr 27 2020, Daniel Kahn Gillmor wrote:
> On Mon 2020-04-27 14:53:07 -0300, David Bremner wrote:
>> Quoting notmuch(1)
>>
>>OPTION SYNTAX
>>All options accepting an argument can be used with '='
>>or ':' as a separator. For the cases where it's not ambiguous
>>
On Mon, Apr 27 2020, David Bremner wrote:
> It turns out the behaviour of inline functions in C header files is
> not a good idea, and can cause linking problems if the compiler
> decides not to inline them. In principle this is solvable by using a
> "static inline" declaration, but this
On Fri, Apr 24 2020, David Bremner wrote:
> Milton Vandersloot writes:
>>
>> [PATCH] Let test_emacs_expect_t respect missing external prerequisites
>>
>> test_emacs_expect_t did not test for missing prerequisites (even though
>> it called test_emacs which does it). Fix that by testing for
json_check_nodes.py exists in source tree, not in out of tree
build tree. Added -B to the execution so source tree is not
"polluted" by a .pyc file when json_check_nodes.py is executed.
When creating run_emacs.sh make it load .elc files from out of
tree build tree, not from source tree if such
When doing out of tree build,
- sphinx-build cannot collect source files from source code
directory and generated files from build directory.
- python3-cffi did not work, did not investigate further.
In order to get at least something done out of tree, these
features are disabled when doing
On Sun, Apr 19 2020, Kirill Elagin wrote:
> Hello,
>
> Notmuch contains a bit of logic for “normalising” the database path: it can
> be relative to $HOME and fallsback to $MAILDIR or $HOME/mail. However, this
> logic is implemented in `notmuch_config_open` and is not available through
> bindings.
Xapian 1.4 is over 3 years old now (1.4.0 released 2016-06-24),
and 1.2 has been deprecated in Notmuch version 0.27 (2018-06-13).
Xapian 1.4 supports compaction, field processors and retry locking;
conditionals checking compaction and field processors were removed
but user may want to disable
{ print }' unsorted_OUTPUT > OUTPUT
> +rm unsorted_OUTPUT
> cat <<'EOF' >EXPECTED
> == stdout ==
> alice
> --
> 2.26.1
> ---
> a better version of the previous patch I sent with head/tail replaced by an
> awk
> script by Tom
On Fri, Apr 17 2020, Olivier Taïbi wrote:
> the "prefix" test in T610-message-property extracts values from a
> (key,value) map where multiple entries can have the same key, and the
> entries are sorted by key, but not by value. The test incorrectly
> assumes that the values will be sorted as
On Tue, Apr 14 2020, di...@santanas.co.za wrote:
> Greetings :)
>
> In notmuch-show-mode, some emails have a date like this: Date: Thu, 09
> Apr 2020 14:34:42 + while others like this Date: Sun, 12 Apr 2020
> 21:04:01 +0200
>
> Is this something I can change in notmuch to always show the
On Mon, Apr 13 2020, Tomi Ollila wrote:
> Previously ' without preceding \ was replaced with `, to make emacs
> document content structure `...' to work with reStructuredText.
The change is good, but comment message crap.
While trying to make rstdoc.el to load elisp code so that in docs
On Fri, Apr 10 2020, Olivier Taïbi wrote:
> the following diff addresses 3 zlib-related bugs in notmuch.
> 3) in gz_getline(), if gz_error sets its second argument to Z_STREAM_END
>then there was no error (only EOF). Unfortunately the zlib manual is
>not very clear on the meaning of
On Mon, Apr 13 2020, David Bremner wrote:
> This will at least catch errors, and can be replaced with more
> sophisticated error handling where appropriate.
> ---
> notmuch-client.h | 4
> notmuch-dump.c | 24
> 2 files changed, 16 insertions(+), 12 deletions(-)
Previously ' without preceding \ was replaced with `, to make emacs
document content structure `...' to work with reStructuredText.
But there are also single uses of ' in parts of the extracted
docstrings, so better "restrict" the matching content to `[^']+'.
Dropped checking preceding \ before
On Sun, Apr 12 2020, David Bremner wrote:
> This will at least catch errors, and can be replaced with more
> sophisticated error handling where appropriate.
> ---
> notmuch-client.h | 3 +++
> notmuch-dump.c | 24
> 2 files changed, 15 insertions(+), 12 deletions(-)
>
On Sun, Apr 12 2020, David Bremner wrote:
> 'qsx' reported a bug on #notmuch with notmuch-dump and large stored
> queries. This test will pass (on my machine) if the value of `repeat'
> is made smaller.
> ---
> test/T240-dump-restore.sh | 13 +
> 1 file changed, 13 insertions(+)
>
>
On Mon, Apr 06 2020, David Bremner wrote:
> Leo Gaspard writes:
>
>> David Bremner writes:
>>
>>> Leo Gaspard writes:
>>>
Hello,
I have recently started conversing with someone whose email client
incorrectly tags PDF attachments as text/plain.
>>>
>>> Hi Leo;
>>>
>>>
On Thu, Mar 19 2020, Daniel Kahn Gillmor wrote:
> Avoid a memory leak in the notmuch command line.
>
> gmime_multipart_encrypted_decrypt returns a GMimeObject marked by
> GMime as "transfer full", so we are supposed to clean up after it.
>
> When parsing a message, notmuch would leak one
On Wed, Mar 18 2020, Daniel Kahn Gillmor wrote:
> GMIME_ENCRYPT_NONE and GMIME_VERIFY_NONE have the same value, but they
> are different enumerated types. So in C, this is a cosmetic change,
> but it is technically correct if we only had stricter typing.
Change consistent with '@@ node_verify',
On Mon, Mar 16 2020, Greg Anders wrote:
> The -D flag to install (used in the Makefile) is GNU-specific and does
> not work on BSD distributions (i.e. macOS). Likewise with the xargs -r
> flag. These changes use portable alternatives to these flags while
> preserving the exact behavior.
Looks
On Thu, Mar 12 2020, Daniel Kahn Gillmor wrote:
> Two years later, I'd like to re-propose this patch that moves nmbug to
> python3.
>
> I have read what PEP 394 says (thanks for the pointer, Trevor!) but in
> practice (a) i do not see debian pointing /usr/bin/python to python3 any
> time in the
On Tue, Mar 10 2020, Dan Čermák wrote:
> Hi list,
>
> I have encountered a test failure caused by the T050-new and T060-count
> tests in the latest openSUSE-Tumbleweed rebuild with Python 3.8 instead
> of Python 3.7. Both tests die with:
>
> --8<---cut
On Thu, Feb 27 2020, Mark Walters wrote:
> Saved searches in notmuch-hello and notmuch-jump can specify whether
> to use search mode or tree mode. This adds an option for them to
> specify unthreaded mode.
LGTM.
Tomi
> ---
> emacs/notmuch-hello.el | 29 +++--
>
On Thu, Feb 27 2020, Mark Walters wrote:
> We have shortcuts S and Z to let the user switch to Search view and
> Tree view with the current search. Add U to let the user switch to
> unthreaded view from the current search, and ensure that S and Z
> switch from unthreaded to search and tree veiew
On Thu, Feb 27 2020, Mark Walters wrote:
> Tree mode allows the user to choose whether to use the split screen
> displaying just the current message or a full screen displaying the
> entire thread. As unthreaded mode is quite different in use the user
> may want a different customisation for this
On Thu, Feb 27 2020, Mark Walters wrote:
> It is likely that the user will want a different line format for
> unthreaded mode from tree mode; in particular the thread structure
> graphics are unnecessary in unthreaded mode.
>
> Add a new customisable variable and set it to something sensible.
On Thu, Feb 27 2020, Mark Walters wrote:
> This commit introduces a new 'unthreaded' search mode where each
> matching message is shown on a separate line. It shares almost all of
> its code with tree view. Subsequent commits will allow it to diverge
> slightly in appearance.
Could have just
On Thu, Feb 27 2020, Mark Walters wrote:
> This adds a --unthreaded option to notmuch show to tell it to return
> the matching messages in an unthreaded order (so just by date).
>
> To make it easier for users, in particular for notmuch-tree.el, we
> output each message with the same "nesting" as
Xapian 1.4 is over 3 years old now (1.4.0 released 2016-06-24),
and 1.2 has been deprecated in Notmuch version 0.27 (2018-06-13).
Xapian 1.4 supports compaction, field processors and retry locking;
conditionals checking compaction and field processors were removed
but user may want to disable
On Tue, Feb 18 2020, Daniel Kahn Gillmor wrote:
> crypto.gpg_path was only used when we built against gmime versions
> before 3.0. Since we now depend on gmime 3.0.3 or later, it is
> meaningless.
>
> The removal of the field from the _notmuch_config struct would be an
> ABI change if that
On Sat, Jan 11 2020, Jani Nikula wrote:
> In most cases the documentation and the notmuch binary will be built
> on the same machine and the same dependencies. Hint at the field
> processor support availability in the man page based on the
> documentation build host.
I have to still grasp the
On Sun, Jan 12 2020, Jani Nikula wrote:
> On Sun, 12 Jan 2020, David Bremner wrote:
>> Jani Nikula writes:
>>
>>> This is a draft patch adding basic configure, build and test support
>>> for the binaries. Everything else is left out for now. It would be a
>>> considerable amount of work to
On Mon, Dec 23 2019, Daniel Kahn Gillmor wrote:
> These tests were an attempt to establish that the content of the
> "Legacy Display" part is the same as the actual protected headers of
> the message. But this is more conservative than we need to be.
>
>
On Fri, Dec 13 2019, Tomi Ollila wrote:
> On Thu, Dec 12 2019, David Edmondson wrote:
>
>> On Wednesday, 2019-12-11 at 13:55:16 -05, Robbie Harwood wrote:
>>
>>> My emacs config contains `(add-hook 'message-setup-hook
>>> 'mml-secure-sign-pgpmime)` as re
On Sun, Dec 08 2019, David Bremner wrote:
> Jorge P. de Morais Neto writes:
>
>> Em [2019-12-06 sex 14:41:22-0500], Daniel Kahn Gillmor escreveu:
>>
>>> As for the variations, i'm kind of of a mind that people who deviate
>>> from the defaults should need to maintain their own deviance
On Thu, Dec 12 2019, David Edmondson wrote:
> On Wednesday, 2019-12-11 at 13:55:16 -05, Robbie Harwood wrote:
>
>> My emacs config contains `(add-hook 'message-setup-hook
>> 'mml-secure-sign-pgpmime)` as recommended in the emacstips
>> https://notmuchmail.org/emacstips/#index14h2
>>
>> However,
On Wed, Dec 04 2019, Daniel Kahn Gillmor wrote:
> This series should apply after "wrap-and-sort -ast" v2 is applied
> (id:20191110173748.25792-5-...@fifthhorseman.net).
>
> In this series, i clean up a few things that i noticed from applying
> dh_missing to the debian packaging. In particular,
On Sat, Nov 16 2019, David Bremner wrote:
> Gaute Hope writes:
>
>>
>> By the way, it does not seem that the API is very far from the
>> previous python API. If it is close enough, perhaps it is possible to
>> get away with a bug version bump in the bindings rather than creating
>> a new
On Sun, Nov 24 2019, David Bremner wrote:
> The documentation for notmuch_config_list_key warns that that the
> returned value will be destroyed by the next call to
> notmuch_config_list_key, but it neglected to mention that calling
> notmuch_config_list_value would also destroy it (by calling
>
On Sun, Nov 17 2019, David Bremner wrote:
> Yes, being root would break some of the tests, e.g. those that rely on
> removing permissions to generate an error. Probably we should just
> document that running the test suite as root is not supported? If
> someone can explain a good reason to run as
On Fri, Nov 22 2019, Daniel Kahn Gillmor wrote:
> On Thu 2019-11-21 08:27:04 -0400, David Bremner wrote:
>> Apologies for being late to the discussion of where to store the
>> configuration. So far we have only stored configuration in the database
>> where it affected the behaviour of the library
In case zlib not found by pkg-config(1) the pkg-config information
is resolved by attempting to print ZLIB_VERSION from from zlib
installation if it exists anyway.
If above done successfully compat/zlib.pc is written for forthcoming
pkg-config execution.
Since `set -u` is in effect (since
On Sat, Nov 16 2019, Johan Parin wrote:
> Modify format_headers_sprinter so that it returns some additional headers
> in the
> sexp, instead of a small fixed set of headers.
>
> The extra header list is configured by the database config option
> `show.extra_headers'.
>
> This is required in
On Thu, Nov 14 2019, Daniel Kahn Gillmor wrote:
> On Wed 2019-11-13 01:30:50 +0200, Tomi Ollila wrote:
>> On Tue, Nov 12 2019, Daniel Kahn Gillmor wrote:
>>
>>> And, I still haven't heard any clear arguments for choosing between
>>> configurability as an absol
hmail.org/git/notmuch David has ref origin/wip/cffi
which contains related changes -- You can fetch the code while waiting
for more collaboration instructions from David.
> On Tue 05 Nov 2019 at 22:22 -0400, David Bremner wrote:
>
>> Tomi Ollila writes:
>>
>>
>>> alte
On Tue, Nov 12 2019, Daniel Kahn Gillmor wrote:
>
> And, I still haven't heard any clear arguments for choosing between
> configurability as an absolute thing or a differential thing. They have
> significantly different impact on adopters over time, as the default
> configuration changes.
I
On Sun, Nov 10 2019, David Edmondson wrote:
> On Saturday, 2019-11-09 at 23:13:58 +01, Johan Parin wrote:
>
>> +const char* interesting_headers[] = { + "Maildir",
>> "Mailing-list", "Tags", "Attachments", "Signature", +
>> "Decryption", "User-agent", "X-Mailer"};
>
> It would be
Subject line not updated
On Sat, Nov 09 2019, Johan Parin wrote:
> So this version only returns a fixed limited set of extra
> headers. Hopefully this eliminates any concern for a performance
> penalty. Of course it limits the usefulness of the
> notmuch-message-headers variable.
headers to
On Fri, Nov 08 2019, David Bremner wrote:
> Tomi Ollila writes:
>
>>
>> Right -- just that pytest-3 may not be available -- to iterate (tested)...
>>
>> if ${NOTMUCH_PYTHON} -m pytest -c $conf --version >/dev/null 2>&1; then
>>
>
> The probl
On Tue, Nov 05 2019, David Bremner wrote:
> Tomi Ollila writes:
>
>
>>
>> probably
>>
>> test_expect_success "${NOTMUCH_PYTHON} -m pytest \
>> --log-file=$TMP_DIRECTORY/test.output \
>> $NOTMUCH_SRCDIR/bind
On Sun, Nov 03 2019, David Bremner wrote:
>
> @@ -32,10 +33,11 @@ def notmuch(maildir):
> """
> cfg_fname = maildir.path / 'notmuch-config'
> cmd = ['notmuch'] + list(args)
> -print('Invoking: {}'.format(' '.join(cmd)))
> +env = os.environ.copy()
> +
On Mon, Nov 04 2019, Tomi Ollila wrote:
>
> as for checking pytest existence, the following works somewhat:
>
>~/test-venv/bin/python3 -m pytest --version
>
> It prints the version, then exists. Could not figure out how to request
> specific version in quick look (10 m
On Sun, Nov 03 2019, David Bremner wrote:
> The entire python-cffi test suite is considered as a single test at
> the level of the notmuch test suite. This might or might not be ideal,
> but it gets them run.
> ---
> test/T391-python-cffi.sh | 12
> 1 file changed, 12 insertions(+)
On Sun, Nov 03 2019, David Bremner wrote:
> Put the build product (and tests) in a well known location so that we
> can find them e.g. from the tests.
> ---
> Makefile.local | 2 +-
> bindings/Makefile.local | 9 +
> 2 files changed, 10 insertions(+), 1 deletion(-)
>
> diff
On Sun, Nov 03 2019, David Bremner wrote:
> This is needed to build the new python bindings
> ---
> configure | 15 +++
> 1 file changed, 15 insertions(+)
>
> diff --git a/configure b/configure
> index 3c148e12..300591fe 100755
> --- a/configure
> +++ b/configure
> @@ -671,6 +671,15
On Sun, Nov 03 2019, David Bremner wrote:
> The entire python-cffi test suite is considered as a single test at
> the level of the notmuch test suite. This might or might not be ideal,
> but it gets them run.
IMO this is good enough approach -- provided that pytest is prereq
for this test to be
On Fri, Oct 25 2019, Aren Tyr wrote:
> Hello all
>
> I have setup mbsync to receive my e-mail, msmtp to send my mail, and use
> notmuch + emacs to read/compose my mail. I have the msmtp-mta package also
> installed, so that msmtp acts as a sendmail replacement. I have a bizarre
> problem,
On Sun, Sep 15 2019, Daniel Kahn Gillmor wrote:
> This patch implements a functional identification and repair process
If there is going to be more versions, then the above could be changed
to either
1) This commit implements...
or just
2) Implement a functional ...
> for "Mixed Up" MIME
On Wed, Sep 11 2019, Daniel Kahn Gillmor wrote:
> In id:87blw1rldy@tethera.net, bremner identified two of my edits
> breaking dme's series that permits asynchronous retrieval of OpenPGP
> keys.
>
> This is a revision of that series that should apply to the current
> master, taking into
On Sun, Sep 15 2019, Daniel Kahn Gillmor wrote:
> mailscripts 0.11 now ships a derivative of devel/printmimestructure
> called email-print-mime-structure. Maintenance for that utility will
> happen in mailscripts from now on, so we should not track an
> independent copy of it in notmuch's source
Whitespace in $NOTMUCH_SRCDIR (and $PWD) may work in builds,
but definitely will not work in tests. It would be difficult
to make tests support whitespace in test filename paths -- and
fragile to maintain if done.
So it is just easier and safer to disallow whitespace there.
In case of out of
301 - 400 of 3694 matches
Mail list logo
