From: Jameson Graef Rollins <jrollins@caltech.edu>
To: "Jorge P. de Morais Neto" <jorge+list@disroot.org>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Tomi Ollila <tomi.ollila@iki.fi>,
notmuch@notmuchmail.org
Subject: Re: moving the config into the database [was: Re: [PATCH] Display extra headers for emacs-mua - db config option]
Date: Tue, 10 Dec 2019 08:11:56 -0800 [thread overview]
Message-ID: <87lfrktb1v.fsf@caltech.edu> (raw)
In-Reply-To: <877e36bryd.fsf@disroot.org>
On Sun, Dec 08 2019, Jorge P. de Morais Neto <jorge+list@disroot.org> wrote:
> Em [2019-12-08 dom 09:12:55-0800], Jameson Graef Rollins escreveu:
>
>> You can already use 'notmuch config list' to dump every configuration
>> item to stdout. Would that be sufficient for personal synchronization
>> purposes.
>
> But then I would have to remember invoking
> ~notmuch config list > ~/notmuch-config~
> every time I changed Notmuch configuration.
Rather than remember, why not just have your synchronization script
retrieve the config at sync time using notmuch config/dump. That way
you don't have to remember to do anything, and you can be agnostic about
how the configuration info is stored on disk.
Fwiw I support dkg's idea to store the config in the database itself. I
think that's a clean simplification that makes a lot of sense.
jamie.
next prev parent reply other threads:[~2019-12-10 16:12 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
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 [this message]
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=87lfrktb1v.fsf@caltech.edu \
--to=jrollins@caltech.edu \
--cc=dkg@fifthhorseman.net \
--cc=jorge+list@disroot.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).