Garbled character displayed on current debug line in normal mode
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Describe the bug
When debugging C++ code in VS Code with the VSCodeVim extension enabled, the visual indicator for the current execution line renders incorrectly. Instead of the standard VS Code marker, a garbled character is displayed, overlaying the code text on the highlighted line.
To Reproduce
Steps to reproduce the behavior:
- Ensure the VSCodeVim extension is enabled.
- Open a C++ project configured for debugging.
- Set a breakpoint on an executable line of C++ code (like the
std::coutline shown in the video). - Start a debugging session (e.g., press F5).
- Step through the code (e.g., using F10) until execution pauses on the line containing the breakpoint.
- Observe the visual indicator for the current execution line.
Expected behavior
The current stack frame indicator should display correctly as defined by VS Code's theme and settings (usually a yellow arrow in the gutter and/or a full line highlight). There should be no unexpected or garbled characters overlaying the code on that line due to the VSCodeVim extension.
Screenshots
Here is a GIF derived from the video showing the issue:
Environment (please complete the following information):
- Extension (VsCodeVim) version:
1.29.0 - VS Code version:
1.98.2 - OS:
macOS 15.4 ARM
Additional context
- The issue appears specifically related to the rendering of the current debug line highlight when VSCodeVim is active.
- Disabling the VSCodeVim extension resolves the issue, and the standard VS Code debug highlighting appears correctly.
- This does not seem related to key remappings, but rather a visual rendering conflict between the extension and VS Code's debugging UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in VS Code 1.98.2 on macOS with VSCodeVim 1.29.0, using a C++ debugging session and stepping with F10 to the breakpoint line. Trace the interaction between VSCodeVim and VS Code's current stack frame highlighting; done means the standard gutter or line highlight appears without a garbled character overlay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100