Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Multiple extensions registering the 'type' command
See original GitHub issue- VSCode Version: 1.5.3
- OS Version: Windows 10
Steps to Reproduce:
- Install and enable VSCodeVim and vscode-jumpy
- Open a file with text
- Run the command
Jumpy Word Mode. Two letter decorations should appear at the start of each word - Type in the two letter code for that word. Jumpy functionality should enact a ‘Jump’ to the cursor position of that decorator.
- It doesn’t work 😦 The keystrokes are being processed by VSCodeVim, not Jumpy.
I am the author of vscode-jumpy (repo). A user has reported that Jumpy does not work in combination with VSCodeVim: wmaurer/vscode-jumpy#1.
It seems that both extensions are doing a registerCommand('type'), but VSCodeVim seems to take priority over vscode-jumpy. Is there are way to manage which extension has priority, so that it can receive and process the keystrokes?
Ideally I want to Jumpy to receive and process the next two keystrokes after enabling Jumpy Word Mode, but then let the rest of the keystrokes forward to VSCodeVim.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:62
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s has been 2 years, still can’t get emacs-keymap work with ace-jump ext, does anyone have solution about this issue ?
Hey, all. May we have this issue updated, please?