On Tue, May 11, 2021 at 08:48:45AM +0200, Michael J Gruber wrote:
> If you sync gmail labels to exact copies in different folders then you're not
> holding it right, sorry ;)
> Gmail is not an IMAP service; it has an IMAP API which exposes labels as
> folders, with all the caveats which this impli
Michael J Gruber writes:
> Due to the change in the config system, notmuch keeps a notmuch database
> open when it would not do so before. Consequently, it can miss changes
> to the database which are done from a hook (while notmuch holds the
> databse in read only mode). When notmuch itself writ
Due to the change in the config system, notmuch keeps a notmuch database
open when it would not do so before. Consequently, it can miss changes
to the database which are done from a hook (while notmuch holds the
databse in read only mode). When notmuch itself writes to the database
after that it us
On Tue, May 11 2021, Felipe Contreras wrote:
> On Tue, May 4, 2021 at 3:25 AM Felipe Contreras
> wrote:
>>
>> On Tue, May 4, 2021 at 3:17 AM Felipe Contreras
>> wrote:
>> >
>> > This superseeds my previous series [1] with much more cleanups.
>> >
>> > An important new change is the move towards
As an emacs user, I use notmuch for searching and indexing my mail, and love
it. The only problem is that every time I open a message in notmuch, it
overwrites my message configuration for sending mails. In particular, it seems
to change my headers, and my completion-methods. I need to reset thi
... just a guess: Could it be that
a9f74aee ("CLI/new: drop the write lock to run the pre-new hook.", 2021-03-18)
was not enough?
notmuch_database_reopen() only reopens the xapian db but does not update
other members in notmuch_database_t *notmuch, such as the last doc id
and thread id.
If a p
Alexander Adolf venit, vidit, dixit 2021-05-11 16:32:22:
> Alexander Adolf writes:
>
> > Michael J Gruber writes:
> >
> >> [...]
> >> So it seems:
> >>
> >> - The mis-threading happens during `notmuch new`, not with `notmuch
> >> reindex`.
> >> - In this new case (and if I remember correctly a
Michael J Gruber writes:
> [...]
> So it seems:
>
> - The mis-threading happens during `notmuch new`, not with `notmuch
> reindex`.
> - In this new case (and if I remember correctly also in the others),
> it's always a new message getting worngly put into an existing thread,
> and if I'm no