Nick Krichevsky

> Weired. This PR is just a more comprehensive ViewPort information, how can it cause new problems It might not be. It could be another PR from master :) Like...

Can this PR be closed, given #1976?

Looking back, it seems that (2) in my above list was a hack to fix this issue https://github.com/vscode-neovim/vscode-neovim/issues/372. The fork of that extension doesn't work anymore, and I couldn't produce...

Thanks for the look guys. Nice to know I'm not completely off-base. I haven't gotten through what I need to in order to fix my cursor manager concerns (and the...

Highlights were a fun problem to solve, given the use of `async` code in there. I stole a concept from Go, [`WaitGroup`](https://pkg.go.dev/sync#WaitGroup)s, to ensure that flush events wait for the...

@theol0403 Absolutely! I'll prefer to do it in line, if that's ok with you. Easy for lots of things to get missed in a stray markdown document.

Oh interesting. I think this may have uncovered a subtle bug as a result of event ordering. It seems like `mode_info_set` is sent after `mode_change`, so when processing the `mode_change`,...

Nope, I just made a silly mistake. I shouldn't be going over the list of events backwards :sweat_smile:. The `splice` in `main_controller` tripped me up

This may have been addressed by version 1.8.3. Can you give that a whirl and let me know if you still experience issues (even better if it's in a reproducible...

That's very strange. I definitely don't experience that locally if I type `/uint32` in a buffer containing the text in that screenshot. Is this with a clean `init.vim`/`neovimClean` enabled? What's...