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
Thanks for this plugin! It's made VSC usable for me as I'm a longtime vim user, attempting to use vscode+vim. In my attempts, a lot of muscle memory has been challenging but configuration settings have helped a ton.
One area I'm befuddled by is, what do I do when I accidentally do something that "crashes" the vim extension?
For example, just now I wasn't sure what project I had open and by habit ran :pwd -- suddenly the keyboard does nothing, the "command" section of the status bar shows my :pwd as entered but I'm unable to do anything. Setting aside the lack of the :pwd command (which #8671 shows as closed, but is not) I assume the plugin has crashed entirely, but what do I do now?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Thanks for this plugin! It's made VSC usable for me as I'm a longtime vim user, attempting to use vscode+vim. In my attempts, a lot of muscle memory has been challenging but configuration settings have helped a ton.
One area I'm befuddled by is, what do I do when I accidentally do something that "crashes" the vim extension?
For example, just now I wasn't sure what project I had open and by habit ran
:pwd
-- suddenly the keyboard does nothing, the "command" section of the status bar shows my:pwd
as entered but I'm unable to do anything. Setting aside the lack of the:pwd
command (which #8671 shows as closed, but is not) I assume the plugin has crashed entirely, but what do I do now?Beta Was this translation helpful? Give feedback.
All reactions