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
For several linters (I've tried ALE with Rust, Go, C, C++ and Python) when there are errors to be displayed in source code, just a single char gets highlighted, instead of whole identifier. It's unconventional compared to other tools, and aesthetically not nice to have highlighting points instead of words. This didn't happen for Rust, but happens for all others I've tried.
Feature request: try highlighting whole identifier when it's sensible to do so (not needed when error is at special char, like extra bracket).
The text was updated successfully, but these errors were encountered:
There's no general solution for this. so I'll close this. ALE already supports specifying beginning and end columns and/or lines for highlights. Each linter needs to be handled separately.
For several linters (I've tried ALE with Rust, Go, C, C++ and Python) when there are errors to be displayed in source code, just a single char gets highlighted, instead of whole identifier. It's unconventional compared to other tools, and aesthetically not nice to have highlighting points instead of words. This didn't happen for Rust, but happens for all others I've tried.
Feature request: try highlighting whole identifier when it's sensible to do so (not needed when error is at special char, like extra bracket).
The text was updated successfully, but these errors were encountered: