Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: notmuch is limited to a single local mail store, right?
Date: Fri, 15 Jan 2016 11:28:10 +0800	[thread overview]
Message-ID: <87wprbldx1.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bn8n1sdq.fsf@gmail.com>

myglc2 <myglc2@gmail.com> writes:

> After more flailing than I care to admit I have notmuch working with
> nnir so that I can do 'G G' on a maildir folder populated/syncronized
> by, for example, mbsync. Pretty, pretty, pretty nice!
>
> In the process of getting this working, I discovered that, to use
> notmuch, you must first consolidate all your mail under a single
> directory which also holds the '.nogmuch' index folder.
>
> Why? Because (according to the notmuch man page) '.notmuch-config'
> specifies a single 'database.path' to maildir (as opposed to a list of
> paths) and 'nnir-notmuch-remove-prefix' is a global variable.

Actually you can set that variable on individual servers, so each server
removes its own prefix.

You still have the problem that notmuch only indexes from a single
parent directory down, though. Have you already collected all your
various maildir servers under one parent directory?

Of course, you'll probably still run into errors: searching on one
server will cause notmuch to return results from *all* servers, then the
server under point will try to remove its prefix from all the results,
and... I don't know what will happen then!

E




  reply	other threads:[~2016-01-15  3:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15  2:36 myglc2
2016-01-15  3:28 ` Eric Abrahamsen [this message]
2016-01-15 12:46   ` myglc2
2016-01-15 13:12     ` Erik Colson
2016-01-15 16:43       ` myglc2
2016-02-06  0:06         ` gnus async prefetch and nnimap Erik Colson
2016-02-06  1:13           ` Eric Abrahamsen
2016-02-06  1:15             ` Eric Abrahamsen
2016-08-01 21:29               ` IMAP changes timestamp when moving an article to another group Erik Colson
2016-08-01 23:49                 ` Greg Troxel
2016-08-05 19:21                   ` Steinar Bang
2016-08-16 13:22                     ` Erik Colson
2017-09-05 16:14                       ` Steinar Bang
2017-09-09  7:47                         ` Steinar Bang
2017-09-09 15:12                           ` Eric Abrahamsen
2017-09-10 10:03                             ` Steinar Bang
2017-09-14 22:29                               ` Eric Abrahamsen
2017-09-15 15:42                                 ` Steinar Bang
2017-09-15 21:52                                   ` Eric Abrahamsen
2018-04-11 20:25                                     ` Lars Ingebrigtsen
2018-04-11 22:08                                       ` Eric Abrahamsen
2016-01-15  5:30 ` notmuch is limited to a single local mail store, right? Adam Sjøgren
2016-01-15  7:49   ` Alan Schmitt
2016-01-15  8:17     ` Adam Sjøgren
2016-01-15 13:03       ` myglc2
2016-01-16  3:56         ` myglc2
2016-01-15 12:50   ` myglc2
2016-01-15 14:25     ` Peter Münster
2016-01-15 19:19     ` Adam Sjøgren
2016-01-15 20:21     ` Adam Sjøgren
2016-01-16  3:47       ` myglc2

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wprbldx1.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).