Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: notmuch is limited to a single local mail store, right?
Date: Fri, 15 Jan 2016 20:19:12 +0100	[thread overview]
Message-ID: <87a8o6bqhb.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87k2nbhuqa.fsf@gmail.com>

myglc2 writes:

>> If you have separate servers, I guess you can have a separate notmuch
>> index per server?

> notmuch does not support making more than one index.

Uhm, you don't have to tell one notmuch instance about the other?

Just run notmuch once against one "server" (using one configuration),
and then run it against the other "server" (using a second
configuration).

The two notmuch indexes won't know about eachother, of course, but
nothing stops you from doing this - just use the --config=FILE command
line option.

>> I would think that you would lose the ability to search across the
>> servers/indexes, but maybe that is what you want, when you split them
>> up?

> I was thinking I wanted to split them up for backup and other purposes.

That makes sense - I was trying to ask you about when you search for
something, do you want to search only within a single "server"?

If so, having a notmuch index for each "server" will not be a problem.
If you want to search across "servers", you'll need something like what
Alan Schmitt wrote.


  Best regards,

    Adam

-- 
 "Sleepwalking!" "Nightmare!"                                 Adam Sjøgren
 "Homocidal psycho jungle cat!"                          asjo@koldfront.dk




  parent reply	other threads:[~2016-01-15 19:19 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
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 [this message]
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=87a8o6bqhb.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).