search

VSCodeVim / Vim

:star: Vim for Visual Studio Code
http://aka.ms/vscodevim
MIT License
13.94k stars 1.32k forks source link

VSCodeVIM not working: command 'type' already exists at _.registerCommand #5318

Open elefthei opened 4 years ago

elefthei commented 4 years ago

Describe the bug Plugin does not work. Escape does not work. Can type into my file while in "Normal" mode, no vim key combinations work. Specific error in Developer console:

console.ts:137 [Extension Host] stack trace: Error: command 'type' already exists at _.registerCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:674:270) at Object.registerCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:977:119) at R (/Users/lef/.vscode/extensions/vscodevim.vim-1.17.1/out/extension.js:9:230907) at Object.t.activate (/Users/lef/.vscode/extensions/vscodevim.vim-1.17.1/out/extension.js:9:235625) t.log @ console.ts:70

Expected behavior The plugin works and I can use VIM mode.

Environment On MacOSX Catalina, VSCodeVIM 0.17.1, VSCode 1.49.2

J-Fields commented 3 years ago

Is this still an issue?

sbjessee commented 2 years ago

This is still an issue for me

[2022-06-06 03:22:22.109] [exthost] [error] Activating extension vscodevim.vim failed due to an error:
[2022-06-06 03:22:22.109] [exthost] [error] Error: command 'type' already exists
    at o.registerCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:29716)
    at Object.registerCommand (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:97:30972)
    at overrideCommand (/Users/skylerjes/.vscode/extensions/vscodevim.vim-1.22.2/extensionBase.ts:559:38)
    at install (/Users/skylerjes/.vscode/extensions/vscodevim.vim-1.22.2/extensionBase.ts:351:3)
    at e.activate (/Users/skylerjes/.vscode/extensions/vscodevim.vim-1.22.2/extension.ts:34:3)
    at _activate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:8180)
    at _waitForDepsThenActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:8122)
    at _initialize (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:7486)

Environment MacOSX Monterey arm64 VSCodeVIM v1.22.2 VSCode v1.67.2

sbjessee commented 2 years ago

I found the conflicting extension was lak132.indent-to-bracket v1.2.2 There's an existing issue on their repo: https://github.com/briankendall/vscode-indent-to-bracket/issues/4

shivanshu-semwal commented 1 year ago

This is another conflicting extension - https://github.com/AdamMaras/vscode-overtype And this is the main issue for type https://github.com/microsoft/vscode/issues/13441

muthursyamburi commented 3 months ago

This is another conflicting extension - https://github.com/AdamMaras/vscode-overtype And this is the main issue for type microsoft/vscode#13441

Thank you so much!!! I was hitting my head on why vim is not working fine and finally I could resolve it! Yes, overtype was the culprit for me, and I am now back into the happy world of VIM!!! Wowwwwww....