Linter: keep old issues list visible while running and preparing new ones

[technic]

Hi,
I have the following workflow case which is currently a bit annoying in the vs code:

I have a linter (pylint in my case) set up and running. So, I have a list of issues reported and want to fix them one by one. I click on the first in the list, jump to the code and start fixing. If it is usual typo, style or white space bug I can do it in one second. But as soon as I've changed some code - Bam! the linter is restarted and all issues are gone. On a large file or codebase it may take around 10s to rerun pylint, and I have to stare at the blank screen waiting for next minor linter warning to reappear.

So my suggestion is the following: run the linter in the background but always show the last available output in the issues list. If it is not up to date mark it somehow (like grey out for example) while still allowing user to interact with it by jump to the line clicks.

[brettcannon]

@technic a work-around for this is to not have linting on save. That way you can manually run the linters when you're ready to check again.

[luabud]

Thanks for the suggestion 👍 but we decided not to move forward with this idea for now, since there is a workaround for it.