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
I have a linter which takes a variable amount of time to run (anywhere between 2 seconds and up to 1 minute), and I would like to have some way of distinguishing between 'linting done, no errors' and 'linting still busy'.
So I made a wrapper which I pass instead of the actual linter, that outputs 'Warning: linter started' first, then runs the actual linter, and then outputs 'Warning: linter finished' and that works once - but since the warnings are persistent and remain visible until a fresh linter execution finishes, the 'linter finished' message from the previous run remains visible, so I still can't tell if the current linter execution is finished after each edit to the file.
Note I originally posted this on vim stackexchange but someone suggested it fits better here and I agree.
The text was updated successfully, but these errors were encountered:
I have a linter which takes a variable amount of time to run (anywhere between 2 seconds and up to 1 minute), and I would like to have some way of distinguishing between 'linting done, no errors' and 'linting still busy'.
So I made a wrapper which I pass instead of the actual linter, that outputs 'Warning: linter started' first, then runs the actual linter, and then outputs 'Warning: linter finished' and that works once - but since the warnings are persistent and remain visible until a fresh linter execution finishes, the 'linter finished' message from the previous run remains visible, so I still can't tell if the current linter execution is finished after each edit to the file.
Note I originally posted this on vim stackexchange but someone suggested it fits better here and I agree.
The text was updated successfully, but these errors were encountered: