-
Notifications
You must be signed in to change notification settings - Fork 163
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
widgets/ansi: fallback to original text in case of parse error #1502
Conversation
I guess a better solution would be to fix this parsing method. |
I agree it would be better to fix the parser too so that correctly formatted emails are well-coloured. But it is always possible to receive badly formatted emails with truely invalid ANSI escape codes that will crash the parser anyway. In this case it is still nice to be able to see the plaintext/unparsed version of those messages. The stacktrace is in the issue #1493:
I don't know whether there is a simpler way to open .eml files in alot, but I simply copy them to my maildir. |
Instead of crashing and leaving the user with a blank screen when trying to open some messages containing non-handled escape codes. GitHub: relates to pazz#1493
@pacien try my new branch on your email please. |
out of interest: what do you use to create ANSI codes? I only ever found |
See my comment: #1503 (comment).
The ANSI codes in the problematic example were generated by the output of a command that ran on a CI service and transmitted as is. Otherwise, I'm trying to use colordiff to add some colours to inline patches that I receive, but adding a mailcap entry like below doesn't seem to have any effect. .mailcap:
|
Instead of crashing and leaving the user with a blank screen when
trying to open some messages containing non-handled escape codes.
GitHub: relates to #1493