Theo Lemay
Theo Lemay
I managed to reproduce the issue that is causing the error on the neovim side. Steps: - `nvim --listen /tmp/nvim` - create buffer with contents: ``` one two ``` -...
Made upstream issue: https://github.com/neovim/neovim/issues/19643
Been using this, and have been experiencing quite a few buffer desyncs. I think the code that counts changes is broken.
These new changes look really promising! A TON of code deleted, and performance is quite improved. No more delay when escaping! It might just be me (and my computer fresh...
I have re-added the dot-repeat hacks. This might cause a bit more escape lag. However, dot-repeat is important enough to support until nvim adds better support for `nvim_buf_set_text`. I'll make...
Sorry for all the noise, this has been a rollercoaster of ideas, workarounds, and issues. # Vscode -> neovim sync Currently, most implementations rely on keeping the dot-repeat hack (make...
Next steps for me: - [x] investigate smartly ignoring cursor updates - [ ] fix edits offset for live editing method - [x] investigate doing hash diffing for neovim-vscode sync...
It is becoming clear that this is two separate changes, for each way of syncing. To avoid delaying this PR, I have separated the vscode -> neovim sync, which seems...
This is ready for review, and barring bugs, should be ready for merge. Summary of changes: - when vscode reports changed document, changes get sen immediately to nvim - in...