Jason Fields
Jason Fields
Looks like we don't currently capture ``
I haven't looked closely, but since VSCode doesn't tell us where folds are, we may not be able to solve this
This was fixed in 1.23.2
~~Likely we're eating that input and need to change a `when` clause to take into account `breadcrumbsActive` and/or `breadcrumbsVisible`.~~
@rickstaa Hitting `/` first allows you to search, is that insufficient for your needs?
@Rustammio If this is still an issue, can you please provide your settings?
I'm not opposed to this idea, but I also think it places too much blame on VSCode's architecture. There's a lot that we can do to improve VSCodeVim's performance. It's...
Yeah, to be clear, I totally agree - extensions which hijack the `type` command shouldn't be on the same thread as other extensions. Perhaps I'm biased because I don't use...
> what performance problems are actually VSCodeVim's fault anyway? Off the top of my head, the main culprits are: - Keeping track of our own undo stack, which requires retrieving...
> If `u` and `` are mapped to VSCode's native `undo` and `redo`, is extension's undo stack mechanism disabled? Nope