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
Often during testing or debugging code you want to make changes to code that will trigger errors that span multiple lines, slow down editing, and make your code look ugly. If you are displaying errors in a file in some other way, such as with the gutter/sign icons, you don't need to see the ugly line highlights to know that you have to fix something.
I think it would a good idea to add a setting for disabling line highlights for very specific error codes, and also with support for matching errors to ignore for highlighting based on the message with regex. This is only an issue for highlights, so we wouldn't need to consider filtering for other ways of displaying errors, in the short term.
The text was updated successfully, but these errors were encountered:
w0rp
changed the title
Disable line highlights for only specific error codes
Disable line highlights for only specific error codes/messages
Jan 23, 2020
@w0rp I'm getting this error when saving files now:
Error detected while processing function <SNR>125_NeoVimCallback[29]..<lambda>19[1]..<SNR>119_ExitCallback[28]..<SNR>118_HandleExit[45]..ale#engine#HandleLoclist[40]..ale#engine#SetResults[19]..ale#highlight#SetHighlights[8]..ale#Var:
line 4:
E716: Key not present in Dictionary: ale_exclude_highlights
Press ENTER or type command to continue
which is related to this work I presume.
Reading the changes I believe ale_exclude_highlights is optional?
Often during testing or debugging code you want to make changes to code that will trigger errors that span multiple lines, slow down editing, and make your code look ugly. If you are displaying errors in a file in some other way, such as with the gutter/sign icons, you don't need to see the ugly line highlights to know that you have to fix something.
I think it would a good idea to add a setting for disabling line highlights for very specific error codes, and also with support for matching errors to ignore for highlighting based on the message with regex. This is only an issue for highlights, so we wouldn't need to consider filtering for other ways of displaying errors, in the short term.
The text was updated successfully, but these errors were encountered: