VSCodeVim / VSCodeVim/Vim

Failed to handle key=<Esc>. [vscodevim.vim]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api vscodevim.vim

Open
#6,807 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

To Reproduce
Steps to reproduce the behavior: Uknown

VSCodeVim version: 1.21.3

Stack trace
Error: Failed to handle key=<Esc>. [vscodevim.vim]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api vscodevim.vim
    at a (/private/var/folders/d7/h6nf76pn2mx9z8x33fgf0vpc0000gn/T/AppTranslocation/9DAE0EA1-2587-465B-A99F-4C184FBA5C52/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:509:620)
    at Object.t.checkProposedApiEnabled (/private/var/folders/d7/h6nf76pn2mx9z8x33fgf0vpc0000gn/T/AppTranslocation/9DAE0EA1-2587-465B-A99F-4C184FBA5C52/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:509:982)
    at x.getConfiguration (/private/var/folders/d7/h6nf76pn2mx9z8x33fgf0vpc0000gn/T/AppTranslocation/9DAE0EA1-2587-465B-A99F-4C184FBA5C52/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:699:923)
    at Object.getConfiguration (/private/var/folders/d7/h6nf76pn2mx9z8x33fgf0vpc0000gn/T/AppTranslocation/9DAE0EA1-2587-465B-A99F-4C184FBA5C52/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:791:3)
    at m.getConfiguration (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/configuration/configuration.ts:193:29)
    at Function.shouldDeleteMatchingBracket (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/common/matching/matcher.ts:159:36)
    at Function.immediateMatchingBracket (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/common/matching/matcher.ts:185:13)
    at doTextEditorEdit (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/transformations/execute.ts:71:40)
    at /Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/transformations/execute.ts:126:11
    at t.ExtHostTextEditor.edit (/private/var/folders/d7/h6nf76pn2mx9z8x33fgf0vpc0000gn/T/AppTranslocation/9DAE0EA1-2587-465B-A99F-4C184FBA5C52/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:503:191)
    at Object.executeTransformations (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/transformations/execute.ts:124:29)
    at I.actionToRecord [as runAction] (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/mode/modeHandler.ts:727:13)
    at I.handledAsAction [as handleKeyAsAnAction] (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/mode/modeHandler.ts:652:43)
    at I.mh [as handleKeyEvent] (/Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/src/mode/modeHandler.ts:471:11)
    at /Users/jonathanhigger/.vscode/extensions/vscodevim.vim-1.21.3/extensionBase.ts:495:53

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the stack from src/configuration/configuration.ts#getConfiguration through src/common/matching/matcher.ts and src/transformations/execute.ts, then reproduce the Esc key handling failure in VS Code. Confirm the completed change by checking that Esc no longer raises the proposed-API error during matching-bracket handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.