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 >