-
-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instead of Linting...
show which linter is actually slow and still running
#1810
Comments
Linting...
show which linter is actually slow ans still runningLinting...
show which linter is actually slow and still running
I feel like we maybe discussed this before? Dejavu. Anyway, I think the idea is good. "This thing is slow" is much better of course than "something is slow". We don't want to have multiple "animations" going on in the status bar, but I doubt that happens a lot (or rather, I hope so). Ideally our view in the status bar is stable, like |
Yeah, for now I just wanted to reuse what we have, and we have |
Well, we always accept that the status bar lags behind what happens in the editor. In my mind it's a question of how much lag to accept before we update that view to say "our mypy result here is out of date, we're waiting for news", and show |
In the expanded state We use the animation to tell it is a transient, momentary state we're in, a static ellipsis is like our |
Yes, totally agree with everything there 👍🏻 |
We have the simple
Linting...
indicator viabusy_indicator_view.py
. Make this more useful by showing which linter is still running, for examplemypy...
. Maybeflake8, mypy...
for multiple linters.I don't know the exact optics here.
...
stands for the animated.
thing we have. Typically only one linter is still running and we could just printmypy...
. If really multiple linters are slow, either switch back to the simplifiedLinting...
or spell all slow linters out likeflake8, mypy...
.The text was updated successfully, but these errors were encountered: