Lucas Hoffmann

https://travis-ci.com/github/pazz/alot/jobs/502418312#L860 It seems that you changed something that needs the docs to be regenerated but did not regenerate them. @pazz maybe we can use a gitlab action or bot to...

The most general way to find out where they are coming from is to search for any common pattern. Does it happen with - different terminal emulators? - different python...

Just to double check that is not some mail received recently that is messing up notmuch (very unlikely): Can you use the notmuch command line or do these commands also...

These headers look fine. Can you post the email header itself? You can find the original file with `notmuch search --output=file ...` then you can be sure that alot will...

I have no osx and iterm2 available. Is there a stack trace together with the errno2 message? Can you post that as well. I don't see any stack trace in...

No I mean the terminal screen. After you quit alot there might some text on terminal. If you have a stack trace there that could help. Does the editor open?...

This looks like it is related to some message in your initial buffer. Can you try to find the message and confirm by starting alot with `alot search id:my-special-message`. Assuming...

That is the file as rendered by notmuch(1). Please upload the raw file from your mail folder. You can find it with `notmuch search --output files id:99aa6841f5fd378b65518716f23457f6b52aea0c.1604845519.git.geliangtang@gmail.com`.

That message looks harmless (it claims to be ascii and actually is ascii). Can you confirm that `alot search id:99aa6841f5fd378b65518716f23457f6b52aea0c.1604845519.git.geliangtang@gmail.com` produces the *original error*? I just reread your https://github.com/pazz/alot/issues/1557#issuecomment-744059973 and...

I also reread the first exception and it seems to fail when encoding to latin1 (instead of decoding from latin1). So what is your `$TERM` and `$LANG` just in case.