Thanks!

I apologize in advance if my understanding of your go code is faulty. It tried implementing the buffer_events.go in pure vim9script:

https://github.com/DanielViberg/lsp/blob/6d134bf51b83e40a4fd27e26c82df55e2f6bd654/autoload/lsp/lspserver.vim#L611-L688

On these lines:

I apologize in advance if my understanding of your go code is faulty.

It's not unlikely the code is unclear/incorrect :)

I might be misunderstanding your question, but I'll lay out the general setup:

• *vimstate is govim's idea of state, based on messages received from Vim.
• (*vimstate).bufChanged is called by Vim when a buffer has changed. It is therefore the job of this method to update govim's notion of what a buffer holds.
• The code you have linked to is indeed mutating the state of the buffer known to govim

So generally speaking the code is modifying the state of the buffer known to the remote process that is govim.

This is all required because govim is running in a separate process, hence needs to maintain some state for efficiency reasons. And bufChanged is essentially a key building block in that, handling deltas from Vim that express the change to buffer contents.

Does that help?