Repeatedly seeing "Disable other keymaps"

[pzelnip]

Issue Type: Bug

I filed microsoft/vscode-sublime-keybindings#98 on the vscode-submlime-keybindings extension as I periodically (every other day or so) get the "Disable other keymaps ("Sublime Text Keymap and Settings Importer") to avoid conflicts between keybindings" prompt.

On that issue it was suggested that "This should only show once when you install/enable a keymap. If you see this repeat without you installing/enabling a keymap, please open an issue for VS Code."

Since I am continuing to see this issue, I am opening this issue on the vscode project itself.

VS Code version: Code 1.25.1 (1dfc5e5, 2018-07-11T15:33:29.235Z)
OS version: Darwin x64 16.7.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	3, 3, 3
Memory (System)	16.00GB (0.02GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron
Screen Reader	no
VM	0%

Extensions (76)

Extension	Author (truncated)	Version
markdown-toc	Ala	1.5.6
EditorConfig	Edi	0.12.4
output-colorizer	IBM	0.1.2
html-css-class-completion	Zig	1.17.1
better-comments	aar	1.2.6
vscode-base64	ada	0.0.1
jenkins-status	ale	0.6.1
project-manager	ale	8.0.0
django-html	bib	1.2.0
emojisense	bie	0.4.1
vscode-importmagic	bra	0.0.6
path-intellisense	chr	1.4.2
bracket-pair-colorizer	Coe	1.0.59
vscode-svgviewer	css	1.4.4
vscode-markdownlint	Dav	0.19.0
vscode-faker	dee	1.3.0
vscode-uriencode	die	0.0.1
githistory	don	0.4.2
jquerysnippets	don	0.0.1
vscode-babel-coloring	dza	0.0.4
gitlens	eam	8.5.3
terraform-autocomplete	erd	0.0.8
auto-rename-tag	for	0.0.15
code-runner	for	0.9.3
docker-explorer	for	0.1.6
seito-openfile	Fr4	1.6.0
gc-excelviewer	Gra	2.1.25
jwt-decoder	igo	0.0.4
csharpextensions	jch	1.3.0
vscode-nuget-package-manager	jmr	1.1.6
presentationmode	jsp	1.1.5
classic-asp-html	jtj	0.1.0
chat	kar	0.4.5
vscode-gist	ken	1.2.1
vscode-gutter-preview	kis	0.13.0
vscode-github	Kni	0.30.0
vscode-view-in-browser	kop	1.0.5
tf-snippets	log	0.5.0
terraform	mau	1.2.3
markdown-shortcuts	mdi	0.8.1
rainbow-csv	mec	0.4.2
vscode-todo-parser	min	1.9.1
mssql	ms-	1.4.0
python	ms-	2018.7.1
csharp	ms-	1.15.2
PowerShell	ms-	1.8.2
sublime-keybindings	ms-	4.0.0
preview-vscode	myh	1.3.0
gradle-language	nac	0.2.3
color-highlight	nau	2.3.0
snippet-creator	nik	0.0.4
autodocstring	njp	0.2.3
vscode-docker	Pet	0.1.0
polacode	pnp	0.2.2
codebucket	pst	0.2.0
java	red	0.28.0
vscode-icons	rob	7.24.0
partial-diff	ryu	1.2.0
jenkinsfile-support	sec	0.1.0
code-settings-sync	Sha	3.0.0
trailing-spaces	sha	0.2.11
vscode-spotify	shy	2.5.1
vscode-fileutils	sle	2.10.3
vscode-hexdump	sle	1.6.0
rewrap	stk	1.9.1
code-spell-checker	str	1.6.10
vscode-djaneiro	the	1.4.2
vscode-java-debug	vsc	0.10.0
vscode-java-pack	vsc	0.3.0
vscode-java-test	vsc	0.7.1
vscode-maven	vsc	0.10.0
vim	vsc	0.15.7
vscode-wakatime	Wak	1.2.3
jinja	who	0.0.8
change-case	wma	1.0.0
markdown-all-in-one	yzh	1.6.0

(3 theme extensions excluded)

[kieferrm]

@pzelnip You get the prompt when you install a new keymap extension while one is already enabled, or when you enable a keymap extension while one is already active. You have at least two keymaps: "Vim" and "Sublime Text Keymap and Settings Importer". Just to make sure, you got the prompt the first time after you installed the Vim keymap. You actually answered with 'Yes' to disable the "Sublime Text Keymap and Settings Importer". You then restarted VS Code and you got the same prompt again without you disabling or enabling any keymap in the meantime and you could verify in the extensions view that the "Sublime Text Keymap and Settings Importer" was indeed enabled?

[kieferrm]

/needsMoreInfo

[vscodebot]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

[TBBle]

I see this problem too, between the Vim Keymap and Open React Component Style which incorrectly categorised itself as a Keymap. However, I said "No" to the disable-other-keymaps prompt, since I didn't want to disable an extension that added a single keyboard shortcut, or disable the Vim key bindings in favour of the one keyboard shortcut.

But I was definitely seeing it on many (but not all) starts of VS Code. It might have been triggered by opening a folder with recommended plugins in its local .vscode settings, causing some kind of extensions rescan? I'm also using the Settings Sync plugin, but it's not set to auto-operate, and the error popped up before I had told it to upload or download my settings.

Since the bug in that other extension's category has been fixed, I don't see this problem any more, so I can't easily test further.

Edit: Thinking about it, in my case the Open React Component Style extension was the one being complained about, which suggests that the error was triggered by an update to the Vim Keymap.

So to specifically address @kieferrm's question, your scenario is accurate for me except that the answer was 'No' to "Do you want to disable X?". I'm not sure if this is the situations @pzelnip is in though.

[chrmarti]

Looking at the code, this might indeed be triggered by updates, not just installs. Needs more investigation.

[sbatten]

verified that updating a keymap extension does not show the notification again