VSCodeVim / VSCodeVim/Vim

Failed to handle key ``: nvim_buf_set_lines: Buffer is not 'modifiable'

Open
#7,958 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:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

VSCodeVim version: 1.23.2

Stack trace
Error: Error making request to nvim_buf_set_lines
    at c.request (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/node_modules/neovim/lib/api/Base.js:76:23)
    at c.setLines (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/node_modules/neovim/lib/api/Buffer.js:86:21)
    at g.syncVSCodeToVim (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/neovim/neovim.ts:133:15)
    at process.patch (node:internal/process/task_queues:96:5)
    at g.statusBarText [as run] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/neovim/neovim.ts:51:88)
    at C.commandLine [as run] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/cmd_line/commandLine.ts:294:19)
    at b.mode [as run] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/actions/commands/commandLine.ts:153:52)
    at b.i [as exec] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/actions/commands/commandLine.ts:33:60)
    at b.execCount (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/actions/base.ts:184:42)
    at N.actionToRecord [as runAction] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/mode/modeHandler.ts:740:47)
    at N.handledAsAction [as handleKeyAsAnAction] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/mode/modeHandler.ts:689:43)
    at N.text [as handleKeyEvent] (/home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/src/mode/modeHandler.ts:506:11)
    at /home/ozkan/.vscode/extensions/vscodevim.vim-1.23.2/extensionBase.ts:359:73

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 in src/neovim/neovim.ts at syncVSCodeToVim, following the stack trace through the command-line and mode-handling entry points. Reproduce the reported nvim_buf_set_lines failure with a non-modifiable buffer and determine the relevant behavior; done means the reported key no longer produces this error.

Written by the indexing model from the issue text.

Assessment

Tech stack
neovim, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.