unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: WIP fix split-config for notmuch-python2
Date: Tue, 26 Oct 2021 23:36:51 -0300	[thread overview]
Message-ID: <20211027023653.3535874-1-david@tethera.net> (raw)
In-Reply-To: <20211026021131.3162922-1-david@tethera.net>

Posting these proof-of-concept patches because I want to go back and
look carefully at some of the API subtleties that arise, mainly the
question of what happens if the user passes a database_path, and the
library finds a config file which conflicts with that path. Currently
the config file wins, which doesn't seem quite right, but might or
might not be easy to fix.

Also I note that fixing the bug with split configurations for _one_ of
the python frameworks isn't handled really well by the tests in a loop
of id:20211026021131.3162922-1-david@tethera.net

I guess a final question is if we should even bother fixing split
configs for the old python bindings? It is a new feature, so in a
sense it's reasonable not provide it in the deprecated bindings.

  reply	other threads:[~2021-10-27  2:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  1:27 problem with message headers in python bindings David Bremner
2021-10-26  1:56 ` David Bremner
2021-10-26  2:11   ` [PATCH] test: add known broken tests for python bindings in split configs David Bremner
2021-10-27  2:36     ` David Bremner [this message]
2021-10-27  2:36       ` [PATCH 1/2] WIP: add python-cffi bindings to path David Bremner
2021-10-27  2:36       ` [PATCH 2/2] WIP/python2: switch to notmuch_database_{open,create}_with_config David Bremner
2021-12-05 12:35 ` problem with message headers in python bindings 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=20211027023653.3535874-1-david@tethera.net \
    --to=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /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).