From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
Johan Parin <johanparin@gmail.com>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] Display extra headers for emacs-mua - db config option
Date: Fri, 22 Nov 2019 03:47:44 +0800 [thread overview]
Message-ID: <875zjdj9jz.fsf@fifthhorseman.net> (raw)
In-Reply-To: <875zjd8lev.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
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 API.
While i'm being ambitious, i'd like also to eventually consider moving
more of the existing CLI functionality into being accessible from the
library. I think this would help downstream MUAs that use notmuch who
currently can't (or don't want to, for whatever reason) take advantage
of the existing CLI, but can use the library.
If we stuff more config in the config file, then the behavior of any
future move to the library will have to grapple with the config move
(currently the library never reads the config file, it just opens the
database).
> I know some people (e.g. dkg) have suggested it would be better to
> store all of the configuration in the database for consistency, while
> others are disgruntled that some of the configuration is not editable
> with text editor.
It would still editable with a text editor -- you just need to edit the
output of "notmuch dump --include config" and feed the result back into
"notmuch restore" :)
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-11-21 20:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 16:27 [PATCH] Display extra headers for emacs-mua - db config option Johan Parin
2019-11-16 16:35 ` Tomi Ollila
2019-11-16 16:53 ` Johan Parin
2019-11-21 2:48 ` Daniel Kahn Gillmor
2019-11-21 12:16 ` David Bremner
2019-11-21 18:29 ` Johan Parin
2019-11-21 21:56 ` Johan Parin
2019-11-22 2:51 ` Daniel Kahn Gillmor
2019-11-22 17:46 ` Carl Worth
2019-11-21 12:27 ` David Bremner
2019-11-21 19:47 ` Daniel Kahn Gillmor [this message]
2019-11-21 21:38 ` Tomi Ollila
2019-11-22 2:43 ` moving the config into the database [was: Re: [PATCH] Display extra headers for emacs-mua - db config option] Daniel Kahn Gillmor
2019-12-08 16:47 ` Jorge P. de Morais Neto
2019-12-08 17:12 ` Jameson Graef Rollins
2019-12-08 18:19 ` Jorge P. de Morais Neto
2019-12-09 18:31 ` Daniel Kahn Gillmor
2019-12-10 12:46 ` Jorge P. de Morais Neto
2019-12-10 17:01 ` Daniel Kahn Gillmor
2019-12-12 11:59 ` Jorge P. de Morais Neto
2019-12-10 16:11 ` Jameson Graef Rollins
2019-12-11 10:53 ` David Edmondson
2019-12-11 14:00 ` David Bremner
2019-12-11 14:21 ` David Edmondson
2019-12-12 16:25 ` Daniel Kahn Gillmor
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=875zjdj9jz.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=david@tethera.net \
--cc=johanparin@gmail.com \
--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).