unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alexis Praga <alexis.praga@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Gnus and notmuch
Date: Thu, 10 Jun 2021 21:03:06 +0200	[thread overview]
Message-ID: <86zgvxwnit.fsf@mailoo.org> (raw)
In-Reply-To: <87fsxpsgpk.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Well, one problem at a time :)
>
> While it should be possible to use a single notmuch installation to
> search two nnmaildir servers, as you're doing, it's also possible that
> this is the source of the problem. Could you also show me your
> ~/.notmuch-config?
>
> These two lines are the source of the problem: gnus-search was able to
> find the article numbers from search hits in the "archive" group, but
> was not able to turn search hits in the "home.alex.mail.free.archive"
> group into article numbers. Usually this means it wasn't actually able
> to locate the files on disk, which usually means there's a mismatch with
> the 'remove-prefix setting.
>
> From the traceback, it looks like you were only searching the
> nnmaildir+gmail:archive group. Do you have any idea why you were getting
> results from home.alex.mail.free.archive?
>
> Eric

(Cc'ing the mailing-list...)

Notmuch is configured to parse a folder containing two maildirs (gmail
and free) like this:

> [database]
> path=/home/alex/mail
> [user]
> name=Alexis Praga
> primary_email=$GMAIL
> other_email=$FREE
> 
> [new]
> tags=inbox;unread;new
> ignore=.nnmaildir
> 
> [search]
> exclude_tags=deleted;spam;
> 
> [maildir]
> synchronize_flags=true
> 
> [crypto]
> gpg_path=gpg

If I setup notmuch to take care of one maildir only and using the same
setup with notmuch, I don't have any errors but I don't have any results
either:
> Group nnselect:nnselect-86eed9eef9.fsf contains no messages
Also, removing "ignore=.nnmaildir" from the configuration of notmuch does not help.

I don'tt really know why it is searching for the other maildir. That's
why I have been restarting emacs and removing ~/.newrrc.el*, hoping it
would resolve some conflict with my previous attempts.

Thanks,

-- 
Alexis Praga



  parent reply	other threads:[~2021-06-10 19:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  8:35 Gnus and notmuch Alexis Praga
2021-06-10 16:21 ` Eric Abrahamsen
     [not found]   ` <865yyly6bn.fsf@mailoo.org>
     [not found]     ` <87fsxpsgpk.fsf@ericabrahamsen.net>
2021-06-10 19:03       ` Alexis Praga [this message]
2021-06-10 21:05         ` Eric Abrahamsen
2021-06-10 21:09           ` Eric Abrahamsen
2021-06-11  8:05             ` Alexis Praga
2021-06-11 16:06               ` Eric Abrahamsen
2021-06-11 16:01 ` Alexandr Vityazev
2021-06-11 18:00   ` Alexis Praga
2021-06-11 18:06     ` Eric Abrahamsen
2021-06-12 14:45       ` Alexis Praga
2021-06-12 16:50         ` Alexandr Vityazev
2021-06-14  7:14           ` Alexis Praga

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=86zgvxwnit.fsf@mailoo.org \
    --to=alexis.praga@gmail.com \
    --cc=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).