You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when I press s, the Quickpick command line popup window shows up (screenshot below), which is not what I want. I tried disabling vscodevim and metaJump behaves as expected (no popup window).
To Reproduce
Remap as above
Press s
The Quickpick command line popup window shows up
Expected behavior
I tried the circumvent this issue with the following remap:
This forces vscodevim to use the command line mode in the statusbar, but it shows E492: Not an editor command: metaGo.gotoBefore. What's worth mentioning is that, before this error, the command runs successfully for a split second, i.e., I can see the editor area dimmed and tags activated.
So my question is, how do I run metaGo.gotoBefore in command line mode?
Screenshots
Environment:
metaJump: v1.4.0
Extension (VsCodeVim) version: v1.22.2
VSCode version: 1.65.0
OS: Linux x64 5.15.25-1-MANJARO snap
Thank you again!
The text was updated successfully, but these errors were encountered:
Greetings. Hope you're doing well. Thank you for checking in this issue. I appreciate any help.
Describe the bug
I'm using metaJump along with vscodevim. I have the following setting:
However, when I press
s
, the Quickpick command line popup window shows up (screenshot below), which is not what I want. I tried disabling vscodevim and metaJump behaves as expected (no popup window).To Reproduce
s
Expected behavior
I tried the circumvent this issue with the following remap:
This forces vscodevim to use the command line mode in the statusbar, but it shows
E492: Not an editor command: metaGo.gotoBefore
. What's worth mentioning is that, before this error, the command runs successfully for a split second, i.e., I can see the editor area dimmed and tags activated.So my question is, how do I run
metaGo.gotoBefore
in command line mode?Screenshots
Environment:
Thank you again!
The text was updated successfully, but these errors were encountered: