-
Notifications
You must be signed in to change notification settings - Fork 248
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
Sublime text not responding #514
Comments
I am using kali Linux |
this can be reproduced on fresh installations of ubuntu. |
Same problem happens in my machine, I'm working on kali linux x32 |
I've found this is usually triggered by using the arrow keys the first time after opening Sublime or uploading code to the Arduino. A temporary workaround is to simply not use the arrow keys, and navigate only with the mouse. However, this is inconvenient and easy to forget, some Sublime features (e.g. parallel editing) only work with the arrow keys, and there ought to be a better way to solve this. I believe during this "frozen" period, Stino is reuploading the code to the Arduino, since it restarts execution once the period ends. Enabling USART prevents the Arduino from restarting like this, but does not reduce the frozen period. The frozen period persists even when the device is not selected, or no device is plugged in, and even when editing files unrelated to the Arduino. A fix for this would be greatly appreciated. Sublime is just generally slower since installing Stino. I used to use it as an all-purpose lightweight plain text editor, but it's no longer fast enough. Is it because of all the extra files for every version of Arduino? If so, perhaps it could be solved by letting users download only the files for the version they need. I'm using macOS Mojave 10.14.6 |
I'm trying to use Stino on a very old notebook with Athlon CPU and lubuntu as a replacement for Atmel Studio. |
After adding stino to sublime . It became very slow and when i click on exit , not responding - force stop pop up is displayed
The text was updated successfully, but these errors were encountered: