You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know how I ended up in this state or if it's again somehow related to older versions of libraries (from Debian), but I found my setup in a state where state changes (eg: tag:unread) were not being synced back to gmail, with push saying:
$ gmi push
receiving metadata (5) ...done: 5 its in 00.081s
resolving changes (5) ...done: 5 its in 00.000s
push: nothing to push
I had followed some other older (closed) issues and made sure to do a fresh sync with the right flags in notmuch.config:
In my case, self.local/nm_relative is . but when I try the query notmuch search path:./** it returns no results, but path:** finds everything (and I only have the gmail-synced e-mail in there).
Anyway, I think it may well not be very applicable to other users, but I wanted to record it here in case anyone else runs into something similar with whatever weirdness is going on with my setup.
The text was updated successfully, but these errors were encountered:
I don't know how I ended up in this state or if it's again somehow related to older versions of libraries (from Debian), but I found my setup in a state where state changes (eg:
tag:unread
) were not being synced back to gmail, with push saying:I had followed some other older (closed) issues and made sure to do a fresh sync with the right flags in notmuch.config:
Anyway, I finally traced it down to needing to do this in remote.py:
In my case,
self.local/nm_relative
is.
but when I try the querynotmuch search path:./**
it returns no results, butpath:**
finds everything (and I only have the gmail-synced e-mail in there).Anyway, I think it may well not be very applicable to other users, but I wanted to record it here in case anyone else runs into something similar with whatever weirdness is going on with my setup.
The text was updated successfully, but these errors were encountered: