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.
>
> Bu
Lauren Weinstein writes:
> OK, it looks like using neomutt on a different machine would solve
> the problem. It isn't immediately clear to me (after digging around
> the docs for a bit) where the repo is that will install neomutt as
> opposed to standard mutt, or how the neomutt .muttrc should be
OK, it looks like using neomutt on a different machine would solve
the problem. It isn't immediately clear to me (after digging around
the docs for a bit) where the repo is that will install neomutt as
opposed to standard mutt, or how the neomutt .muttrc should be configured
to simply search and v
Lauren Weinstein writes:
> 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 hierarch
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 fro
Lauren Weinstein 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 so
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 nati
Hi. No, the local mutt is sufficiently customized that switching
to another version is a no-op. I also have been trying the mh2maildir
script (though I had hoped to avoid this, and don't know if I'd
still have the same problems with duplicate messages in the mh
hierarchies causing apparent notmuc
Lauren Weinstein writes:
>
> Attempts to search with the same notmuch-mutt macro after the mh
> hierachies are added in are totally confused. There are many
> link errors during the serach ("file already exists" references mh mail
> message file numbers), and the resulting messages list in mutt i
On Wed 2017-07-05 23:26:18 +0300, Tomi Ollila wrote:
> On Sat, Jun 03 2017, David Bremner wrote:
>
>> I can't see the space in the output of gpg -K --with-colons
[...]
> You could add a variable which is set to ' ' when gmime_2 is used and ''
> when gmime_3 is used and insert that just like '"$FIN
Lauren Weinstein writes:
> Greetings. I've just installed notmuch and notmuch-mutt, obviously
> for use with mutt. Notmuch was initially setup pointing at my
> home Maildir directory, and setup ran fine. My testing within mutt using
> notmuch-mutt macros also worked OK. So far, nifty. Great work!
Hi David, notmuch developers,
* David Bremner [03. Jul. 2017]:
> Try setting a break in _notmuch_database_log (b _notmuch_database_log)
> and run "bt" at that break point. It might (or might not) be worth
> continuing after the first breakpoint to inspect other errors.
I did so with newest notmuc
12 matches
Mail list logo
