anaconda
anaconda copied to clipboard
Show linter error when I am on the error line
Expected Behaviour
Show linter error when I am on the error lines like:
Actual Behaviour
You can only see the linter marks, but not error information. So you have no clue on what is wrong.
Steps to Reproduce
Create the file:
if 'LOG_FILE_NAME' in globals():
# Clear the log file contents
open(LOG_FILE_NAME, 'w').close()
ST3, Anaconda and OS versions
ST3 Console Logs
Anaconda's JsonServer Logs
Note: Anaconda's JsonServer logs can be found in:
- Linux: ~/.local/share/anaconda/logs
- OS X: ~/Library/Logs/anaconda
- Windows: %APPDATA\Anaconda\Logs
No, you don't have to guess the errors, that would be beyond stupid. Actually you have four ways to know about the errors.
- Method 1: Just select the offending line and an error description will appear in the status bar
- Method 2: Use the Command Palette to execute:
Anaconda: Show error list
- Method 3: Set the
anaconda_linter_show_errors_on_save
option totrue
in the config - Method 4: Set the
anaconda_linter_phantoms
option totrue
to see errors inline
As you can see, you don't have to guess too much, have you?
Ok, however the phantoms always show up. Which is horrible. They show only appear when I select the line or hovers it. Following this, the Sublime Text pop up could be used instead of phantoms:
Then this is a feature request and not an issue, not a support request, honestly I think there are already more than enough ways to get information about the linting problems, apart from that, new features are closed till I release Golconda and I can not use the already low spare time that I have implementing and supporting new features.
Said that, I will accept a PR implementing this (always than the person that implements it commit to maintain it as well).
I know this is an old thread but just seeing if anyone here worked on this. This would be a useful feature.
I fixed this by using https://github.com/palantir/python-language-server with https://github.com/tomv564/LSP which already has this implemented.
No wonder i ended up here. Still not solved in 2020 :)