How to differentiate between style and syntax errors? #4596
-
I am new to ALE and my main goal for using this plugin is that I want to see syntax and name errors (such as undefined variables) in my Python code before actually running it. Adjusting my code according to style guides is not my main priority. In fact, some style recommendations (like the insertion of blank lines at many locations) might even hinder me because I have a visual impairment, hence I have to use a magnifier and only small portions of code fit on my screen at once.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
ALE linters can add a For disabling particular errors or warnings, configure the tool itself to do that with its own project files. |
Beta Was this translation helpful? Give feedback.
ALE linters can add a
subtype
key value forstyle
to indicate if errors are warnings are for style or not. Wherever you see they don't, open issues for them or create pull requests. Check out:help ALEStyleError
.For disabling particular errors or warnings, configure the tool itself to do that with its own project files.