unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Bart Trojanowski <bart@jukie.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 3/3] change config file location to be ~/.notmuch/config
Date: Sun, 22 Nov 2009 18:14:20 -0500	[thread overview]
Message-ID: <20091122231419.GA8322@finestructure.net> (raw)
In-Reply-To: <20091122222453.GM17268@jukie.net>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Sun, Nov 22, 2009 at 05:24:53PM -0500, Bart Trojanowski wrote:
> I totally agree with Jamie about the config rename.  I don't know if I
> agree with the database location change... but I might just need some
> convincing.

So I don't really like having the database stored in the maildir.
There are a couple reasons for this:

- I would prefer to keep all notmuch stuff together, including all
  config files, data files, etc.  In my opinion, this just makes
  things easier to keep track of.  No need to guess where any relevant
  notmuch data is if it's all stored together in one place.

- I would prefer to not clutter my mail directories with anything
  that's not mail.  The notmuch database is definitely related to my
  mail, but it's not exactly my mail, so I'd rather keep it somewhere
  else.  (I think there's a whole other thread to be started about
  this, because I think the config should also hold the location of
  the maildir to be indexed, not the path to the index itself, which
  then makes implicit assumptions about where the maildir is.)  This
  point is also probably related to the fact that I've had to change
  MUAs too many times to trust one indefinitely.  So basically I want
  to keep my mail wholly separate from anything that's processing it.

I think Carl said he wanted to keep the ability to specify exactly
where the database is stored, so if we could move away from something
that makes any implicit assumptions about relative paths between the
database and the maildir, then all should be ok.

> Would it be enough to just read .notmuch/config and fall back to
> .notmuch-config otherwise?

Yes, this is a good idea.  I'll try to come up with a patch for this.

jamie.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2009-11-22 23:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 21:58 [PATCH 1/3] remove Makefile.config from source to allow for custom config Jameson Graef Rollins
2009-11-22 21:58 ` [PATCH 2/3] modify notmuch_setup_command to return 1 if config file write fails Jameson Graef Rollins
2009-11-22 21:58   ` [PATCH 3/3] change config file location to be ~/.notmuch/config Jameson Graef Rollins
2009-11-22 22:15     ` Jameson Graef Rollins
2009-11-22 22:24       ` Bart Trojanowski
2009-11-22 23:14         ` Jameson Graef Rollins [this message]
2009-11-23  4:55           ` Carl Worth
2009-11-24 10:55             ` Jan Janak
2009-11-26  3:29           ` Carl Worth
2009-11-26  3:27     ` Carl Worth
2009-11-26  3:24   ` [PATCH 2/3] modify notmuch_setup_command to return 1 if config file write fails Carl Worth
2009-11-26  3:23 ` [PATCH 1/3] remove Makefile.config from source to allow for custom config Carl Worth

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=20091122231419.GA8322@finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=bart@jukie.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).