-
Notifications
You must be signed in to change notification settings - Fork 44
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
Random errors due to no selection #116
Comments
Can you add this after line
Then check your ST console for the output? What I want to find is the value of |
I don't have a way to reproduce it at the moment but "truthy" check is not enough due to how Selections object is implemented in ST. It defines:
which doesn't check number of selections. The 3.8 plugin host does:
but that fix didn't trickle down to the old host. So the explicit |
Oh, that's not normal in Python but I was assuming it behaved like a Python list. I'll submit a patch now. |
Fixed in v11.0.8 released just now. |
I'm randomly getting errors like:
It's not really that important how it's triggered IMO because in the ST API it's not guaranteed that selection is non-empty so plugin should never assume so and always check first.
The text was updated successfully, but these errors were encountered: