Vladimir Panteleev <[email protected]> writes: > notmuch-tree did not protect against concurrent refreshes like > notmuch-search, meaning, hitting '=' (notmuch-refresh-this-buffer) > quickly will spawn multiple parallel notmuch processes, and clobber > the existing results in the current buffer. >
pushed d _______________________________________________ notmuch mailing list [email protected] https://notmuchmail.org/mailman/listinfo/notmuch
