-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mailcap handler for plain/text requiring a tty crashes alot 0.9.1 #1544
Comments
Looking at the bisected commit, I suspect that you have set up a text/plain mime entry that is used without your knowing. Check your |
Hi o/ Thanks for your message. That's correct; indeed I have I have added an entry for text/plain (as provided in the reference commit message) and this solves my issue. However, I feel like a message like "opened with %s" should be displayed. In any case, an incorrect mailcap configuration should not freeze the interface. |
Also, I just noticed that the order between |
You mean the order in which these are listed in the mailcap?
Yes, I think that is relevant but standard behaviour for anything that uses mailcaps: the first match wins.
|
In NixOS 20.09, alot was updated to version 0.9.1. Since alot 0.9.1 it is possible to specify a mailcap for text/plain. This was delegating it to xdg-open, which in turns delegates it to nvim. which probably tried to take control of the tty and crashed alot (see pazz/alot#1544). This adds an explicit entry for text/plain. Mind that the order in which alot matches this file seems to be important. This is probably a bug, but fixed here as a workaround. Signed-off-by: Roosembert Palacios <[email protected]>
Describe the bug
I cannot open any thread from the search view. When I try opening a thread, the thread view is displayed and so are the message headings (incl. title, date and tags), but not any of the message bodies; at this time the interface is completely frozen and I'm forced to C-c the application.
Software Versions
To Reproduce
Steps to reproduce the behaviour:
No error log whatsoever.
After bisecting alot, the problem was introduced by commit b1c93c4. But I am unable to fix the problem myself.
The text was updated successfully, but these errors were encountered: