[Bug] v0.0.90 breaks `workbench.action.compareEditor.nextChange` and `workbench.action.compareEditor.previousChange`
See original GitHub issuev0.0.90 is causing workbench.action.compareEditor.nextChange
and workbench.action.compareEditor.previousChange
not working properly (instead of jumping to the change, the viewport twitches), v0.0.89 does not, the code causing this issue is from #919.
I use these two shortcuts all the time when comparing diffs, so it was easy for me to spot:
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to go to next changes in VS Code side-by-side view?
You are looking for workbench.action.compareEditor.nextChange ... You can simply press F8 Key for go to Next Change. Previous Change in ...
Read more >October 2022 - Visual Studio Code
Tired of accidentally breaking links or images in your Markdown when you move ... MarkdownString( `A command link: [Open setting](command:workbench.action.
Read more >neovim - OnlyABug.com
[Bug] v0.0.90 breaks workbench.action.compareEditor.nextChange and workbench.action.compareEditor.previousChange. v0.0.90 is causing workbench.action.
Read more >vscode-neovim - bytemeta
[Bug] v0.0.90 breaks `workbench.action.compareEditor.nextChange` and `workbench.action.compareEditor.previousChange`. sudoandros. sudoandros CLOSED.
Read more >Key Bindings for Visual Studio Code - vscode-docs
kb(workbench.action.showErrorsWarnings), Show Errors and Warnings, workbench.action.showErrorsWarnings. kb(editor.action.marker.next), Go to Next Error or ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah #919 was released as I felt the pros outweighed the cons (proper lightspeed support). Originally I was not going to release as I also changed c-u/c-d bindings but I was able to separate the changes.
This will be fixed by #993. Until then use an older version of the extension, I made many incremental releases so it’s easy to pick.
Reproducible in 0.0.92+, not in 0.0.91, seems like a regression bug, please reopen this and take a look @theol0403