From: Lauren Weinstein <lauren@vortex.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org, Stefano Zacchiroli <zack@debian.org>
Subject: Re: maildir and nmh/mh
Date: Thu, 6 Jul 2017 19:29:58 -0700 [thread overview]
Message-ID: <20170707022958.GA14649@vortex.com> (raw)
In-Reply-To: <20170706185448.GA25979@vortex.com>
I've got "alot" working well enough for my purposes now ("good enough
for jazz!"). Thanks all!
L
On 07/06 11:54, Lauren Weinstein wrote:
>
> I'll have to see what I can dig out, but it's not immediately clear
> that I can separate out individual folders that will trigger the problems.
>
> But this does suggest another possibility. Assuming notmuch is
> actually accurately indexing the two massive mh hierarchies, is there
> some other simple front end I could use for the (occasional) searches
> I'd like to do on the mh mail archive? Mutt is working fine for the
> more recent maildir messages. If I need to keep the mh messages
> separate (e.g., under some other username and a separate notmuch db)
> and use a different front end to search and view them, that will work.
> I won't need this every day! In fact, keeping the mh messages separate
> from the maildir messages is probably good for other reasons. Thanks.
>
>
>
> On 07/06 15:47, David Bremner wrote:
> > Lauren Weinstein <lauren@vortex.com> writes:
> >
> > > After fixing the find syntax I got mh2maildir working. However, it does not
> > > appear practical in my situation, since I'm dealing with more than 25 years of archived
> > > mh messages! The conversion would take ages with too many manual exceptions.
> > > So unless there's some way to correctly index these natively with notmuch, I guess
> > > this is a dead end. But thanks.
> >
> > For what it's worth, I suspect the problem is not with notmuch proper
> > but with the notmuch-mutt script. Unfortunatately zack (in copy) is
> > really the only one who knows very much about the script. If you could
> > make a small tar ball of an MH directory that causes problems for
> > notmuch-mutt, zack could probably be tricked into looking at it.
> >
> > d
>
>
>
>
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
>
next prev parent reply other threads:[~2017-07-07 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 1:01 maildir and nmh/mh Lauren Weinstein
2017-07-06 13:28 ` cesar mena
2017-07-06 18:36 ` Lauren Weinstein
2017-07-06 18:47 ` David Bremner
2017-07-06 18:54 ` Lauren Weinstein
2017-07-06 19:03 ` David Bremner
2017-07-06 19:24 ` Lauren Weinstein
2017-07-06 21:23 ` David Bremner
2017-07-07 2:29 ` Lauren Weinstein [this message]
2017-07-06 14:18 ` David Bremner
2017-07-06 15:22 ` Lauren Weinstein
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=20170707022958.GA14649@vortex.com \
--to=lauren@vortex.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=zack@debian.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).