-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Run fix in some sort of background thread? #24
Comments
I think SublimeLinter-contrib-xo/linter.py Line 172 in 92aa8b3
on_pre_save_async instead. But I haven't tested.
https://www.sublimetext.com/docs/3/api_reference.html // @LuKks |
@sindresorhus looks promising! I'm happy to give it a test on my project if someone can publish some sort of pre-release |
@sindresorhus is there a way I can try this out? I've tried modifying the |
Ok, confirmed that the change has been made with some logging, unfortunately it doesn't seem to fix the locking issue :( . Been trying to compare to the prettier plugin which does similar stuff but don't yet understand python well enough to spot the difference. |
I tried just changing to |
Hi @IPWright83, did you find any solution to this issue? |
@rocktimsaikia I didn't. Though I've moved company and we just use eslint. It doesn't seem to have the same problems as the xo linter. Save in build seems to work fine without blocking. |
I've tried enabling the
fix_on_save
flag today, which is really great, but it massively slows down the editing experience. Sublime locks for somewhere between 1-2 seconds while it processes this.Is there anyway that this can be ran in some sort of background thread so Sublime remains responsive through this duration?
The text was updated successfully, but these errors were encountered: