<leader> shortcut suspensive when running tests
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
I have the following mapping in settings.json:
{
"before": [
"<leader>",
"r",
"t"
],
"commands": [
"go.test.cursorOrPrevious"
]
},
When I trigger it, the VSCode console opens and the test runs, but the editor completely blocks until the unit test finishes running. On the other hand, if run the test in any other way, namely:
- With a non-Vim VsCode shortcut
- Execute
go.test.cursorOrPreviousfrom the command palette - Click on
run testabove the function signature
The editor is modifiable as expected while the test is running with the open console.
To Reproduce
Add the same shortcut (or any based shortcut) and try using it on a Go test.
Expected behavior
Editor keeps working normally while the test is running.
Environment (please complete the following information):
| CPUs | Apple M2 Max (12 x 24) |
|---|---|
| GPU Status | 2d_canvas: unavailable_software canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: disabled_software multiple_raster_threads: enabled_on opengl: disabled_off rasterization: disabled_software raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: disabled_software video_encode: disabled_software webgl: unavailable_software webgl2: unavailable_software webgpu: unavailable_software |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 64.00GB (11.44GB free) |
| Process Argv | --crash-reporter-id 29f86409-d4c3-4ec3-b87c-41eb83c2ba6c |
| Screen Reader | no |
| VM | 0% |
- Extension (VsCodeVim) version: 1.27.2
- VSCode version: Version: 1.86.2 (Universal)
- OS: MacOs Sonoma 14.3.1 (23D60)
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 with the settings.json mapping for , r, t and the go.test.cursorOrPrevious command. Compare it with the non-Vim shortcut, command palette, and run-test invocations while checking how VSCodeVim handles leader mappings; done means the editor remains modifiable while the Go test runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100