Sublime Forum

find_next cmd+g must be entered twice to function

#1

I have an odd issue that exhibits the following behaviors in OSX (10.8.3) using ST2 (2.0.2 build 2221).

All relates to find_next command.

  1. Hitting cmd+g/super+g (default for find_next) will only send the find_next command after the second consecutive entry of the keyboard command.
  2. This behavior appears to reset after ~2s, wherein if I hit cmd+g repeatedly and the find_next command is registered on the second consecutive entry, if I then wait ~2s I will need to enter the command twice consecutively again to register the command.
  3. If I enter cmd+g and follow it immediately with find_prev, the find_next command will execute before the find_prev. The observed behavior of this is that the current find selection is reached again, as one would expect with consecutive find_next and find_prev calls. If I wait ~2s between the cmd+g and cmd+shift+g (find_prev), the find_next will not execute.
  4. This behavior is not exhibited if the keyboard command for find_next is changed.
  5. this behavior is not exhibited within any other application. Only Sublime Text 2.

Hope the explanation is sufficient but not overly complex. It’s a very odd behavior, and I’m curious if anyone had a suggestion. It’s pretty annoying to have to hit cmd+g twice if I pause traversal more than 2s

0 Likes
#2

Maybe a plugin has bound something to “super+g,super+something else”?

0 Likes
#3

Interesting. So I had begun by removing all packages, then became frustrated when the likely culprits (those with obvious keybindings) didn’t have any affect. I just went and removed all packages, which cleared the issue, and checked iteratively for the issue to reappear with each reinstall.

The problematic extension is sublime-github, via https://github.com/bgreenlee/sublime-github/blob/master/Default%20(OSX).sublime-keymap

Its super+g key sequence grouping was swallowing the command silently!

Time to PR, I suppose.

0 Likes