VSCodeVim / VSCodeVim/Vim

Mark not set

Open
#7,611 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.22.2

Stack trace
Error: Mark not set
    at Function.fromCode (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\error.ts:94:14)
    at c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\vimscript\lineRange.ts:152:28
    at h.resolve (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\vimscript\lineRange.ts:126:18)
    at f.resolve (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\vimscript\lineRange.ts:310:29)
    at l.allMatches (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\vimscript\pattern.ts:82:34)
    at M.getSubstitutionDecorations (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\cmd_line\commands\substitute.ts:267:30)
    at C.getDecorations (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\cmd_line\commandLine.ts:253:22)
    at j.updateSearchHighlights (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\mode\modeHandler.ts:1141:36)
    at j.updateView (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\mode\modeHandler.ts:1545:49)
    at j.handleSelectionChange (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\mode\modeHandler.ts:290:20)
    at job (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\extensionBase.ts:324:38)
    at o.start (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\node_modules\queue\index.js:145:17)
    at o.push (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\node_modules\queue\index.js:59:12)
    at Object.enqueueTask (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\src\taskQueue.ts:55:20)
    at listener (c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\extensionBase.ts:324:17)
    at c:\Users\EAlvarado\.vscode\extensions\vscodevim.vim-1.22.2\extensionBase.ts:612:5
    at u.invoke (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:145)
    at v.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:1856)
    at N.$acceptEditorPropertiesChanged (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:86:67639)
    at i._doInvokeHandler (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:89:13826)
    at i._invokeHandler (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:89:13510)
    at i._receiveRequest (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:89:12171)
    at i._receiveOneMessage (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:89:10841)
    at c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:89:8947
    at u.invoke (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:145)
    at v.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:1856)
    at d.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:19034)
    at c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:104:34275
    at u.invoke (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:145)
    at v.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:1856)
    at d.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:19034)
    at o._receiveMessage (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:23615)
    at c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:21149
    at u.invoke (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:145)
    at v.fire (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:58:1856)
    at v.acceptChunk (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:15865)
    at c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:66:14995
    at Socket.P (c:\Users\EAlvarado\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:104:13797)
    at Socket.emit (node:events:390:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at Pipe.onStreamRead (node:internal/stream_base_commons:199:23)

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 reading src/error.ts at the reported line and the mark-resolution path in src/vimscript/lineRange.ts. Trace how that error reaches src/cmd_line/commands/substitute.ts and src/cmd_line/commandLine.ts during view updates. Done means the reported scenario no longer produces an unhandled “Mark not set” error, but the issue does not provide enough reproduction detail to verify it.

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.