-
Notifications
You must be signed in to change notification settings - Fork 40
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
Problems after updating to macOS Sequoia #6537
Comments
Sounds familiar. I've said this before: command in a text version: {
"keys": ["super+alt+left"],
"command": "prev_os_tab",
}, I've disabled/changed the key-binding which improved the situation to the point that I don't notice it anymore but I'm not sure if it fully eliminated it or just made it better. I can still reproduce this on that laptop after enabling that command and restarting ST and holding left arrow to move the cursor. macOS 15.1.1 here EDIT: And I guess it doesn't reproduce in safe mode because it appears that a restart of ST is required to reproduce which is not possible in safe mode. |
I'm glad I'm not the only who has noticed this. Thank you for replying! For clarity, for other folk, I'm experiencing this for all key presses, not just the arrow keys. But I can imagine the issue is more pronounced if one held down an arrow key and the rapid fire stream of input is converted into delayed, chunked out, sputtered, blasts of what was originally captured. The above comment got me thinking about experimenting with various macOS settings. I tried with all keyboard shortcuts I could find turned off. I tried Function Keys toggled to both using and not using F1, F2 etc. I toggle off all focus related items I could find. I toggled off any extemporaneous keyboard or Finder navigation option I could find (there are a ridiculous number of them at this point) but nothing has remedied the issue. |
Can you reproduce the issue in safe mode (hold option while opening ST from the dock)? |
Great suggestion. The issue goes away completely while in safe mode. What does that imply? |
Well, in my case the issue seems to be related to custom keybinding so could be the same for you (either your own or coming from some installed packages). |
I'll try tearing everything down and re-installing the few packages I have. // /Library/Application\ Support/Sublime\ Text/Packages/User/Package\ Control.sublime-settings
// /Library/Application\ Support/Sublime\ Text/Packages/User/Preferences.sublime-settings
Nothing in key mapping.... |
I'm wrong. I just nuked Sublime Text and all supporting files. Reinstalled it from scratch. Then I ran it unmodified "out of the box" and it still feels janky and has intermittent slow response times to key presses. I might roll back to macOS Sonoma. |
At least in past such slow updates were often caused by broken OpenGL drivers. Does disabling hardware_accelleration improve situation? |
I restarted my computer and now it's working normally. I'm not sure what fixed it. I assume the two packages I had installed previously or the previous settings from Preferences.sublime-settings. Thank you for suggesting trying Sublime Text out in safe mode. Reinstalling Sublime Text, then re-adding customizations, then restarting computer fixed it somehow. |
Side note, since using Sublime Text reinstalled, my muscle memory fingers are attempting to switch Sublime windows with command ` (tick) and it no longer works. I could have sworn this worked before because my fingers REALLY want to switch windows this way. Now I'm not sure if that was something custom I had setup previously or if that is something Sublime had natively before. Either way, it doesn't work anymore. Makes me wonder if that was somehow related to the bug I was having. I asked AI about it and it gave me this (which could be wrong, granted)....
Is this correct, is there no way to switch Sublime windows via a keyboard shortcut? Did I setup something custom? |
What you are looking for is probably "Switch Window" package. |
New information regarding this issue. As soon as I entered my Sublime license, the keyboard lag issue came back. |
⌘` is a macOS system-level keyboard shortcut. Have a look in System Settings to ensure that it's enabled (should be called "Move focus to next window" or similar) |
I checked that setting it was indeed off, that works again now, as per normal. Thank you for the suggestion. Turns out that was not related to the core issue. The core issue still exists - supper laggy response to keyboard input. |
I removed all packages including Package Controller and I unregister Sublime Text and the issue still persists. |
When I open the Sublime from the dock with option key held down (safe mode, with warning popup dialog) it continues to be laggy. I must have had a false positive when I had tried this before. In safe mode key presses are laggy/sticky/burpy |
Description of the bug
After updating laptop to MacOS Sequoia 15.1.1 (24B91) Sublime is now supper laggy with response to keyboard input, to the point of being unusable. When I type the characters show up in the document 2-3 seconds after they are typed. No characters show up on the screen and then 10 of them are dumped into the document all at once.
Other text editors are not having a problem, e.g. TextEdit, Visual Studio Code, so this is not a keyboard problem. This is a Sublime Text + macOS update problem.
Any advice on how to fix this is appreciated. Maybe some OS setting can be disabled? This smells like a macOS bug that is impacting Sublime Text, not the other way around. Could the Sublime maintainers please reach out to Apple to see what has changed that broke the input signal flow for Sublime Text?
Side note: Laptop is a Apple M2 Pro
Steps to reproduce
Expected behavior
When typing character, the characters appear in the document instantly.
Actual behavior
When typing character, they don't show up, then show up all at once in a bundle.
Sublime Text build number
4180
Operating system & version
macOS Sequoia 15.1.1 (24B91)
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response
The text was updated successfully, but these errors were encountered: