unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: Jameson Graef Rollins <jrollins@caltech.edu>,
	"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: Wed, 11 Dec 2019 10:53:06 +0000	[thread overview]
Message-ID: <m2fthrcewd.fsf@dme.org> (raw)
In-Reply-To: <87lfrktb1v.fsf@caltech.edu>

On Tuesday, 2019-12-10 at 08:11:56 -08, Jameson Graef Rollins wrote:

> 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.

I'm not inherently against this, but I'm unsure exactly how it would
work.

For example, I set new.tags and new.ignore in my current
.notmuch-config. If they move into the database, how will I set them
before I have a database?

It seems that only “notmuch new” is currently prepared to create a new
database, but it will also import all of my email before I have a chance
to set the above parameters.

It seems that the obvious answer is “notmuch config” will create a
database if necessary. Is that the plan?

dme.
-- 
They like the smell of it in Hollywood.

  reply	other threads:[~2019-12-11 10:53 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
2019-12-11 10:53                 ` David Edmondson [this message]
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=m2fthrcewd.fsf@dme.org \
    --to=dme@dme.org \
    --cc=dkg@fifthhorseman.net \
    --cc=jorge+list@disroot.org \
    --cc=jrollins@caltech.edu \
    --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).