atanda rasheed

> Unfortunately that's not viable, the engine needs to be built for the exact elixir version that is going to run it. I learned this the hard way a while...

Hi @mhanberg @doorgan, I thought to nudge you that the implementation was updated. I don't know what your thoughts are, except that you're still inclined to find a fix that...

Hi @doorgan, I've tested the fix you made, and everything works just fine. I would go ahead and close this PR.

> Just a note that this issue existed in lexical for a while, so maybe the fix might be similar to the one that was applied to lexical at the...

@mhanberg @doorgan So, I made a change to the cloned expert repo. I added a couple of log statements that show the content changes received from the client (Neovim) and...

So, I was able to trace the whole flow, and I got to find out that Neovim has this concept of incremental updates, and that's the reason for different edits...

Guess what?! I think I've resolved the following issues: 1. Letter reordering problem 2. Formatting wrangling the inner representation of the document 3. I don't need to turn off incremental...

> Just to confirm, is the fix also solving the "typing fast causes reordering problem" Yes, it does. But I've seen cases where I generate a new release, but the...

Just a quick update, while doing some other work, I started experiencing the same issue, but at reduced frequency. The next place I would be looking is Neovim, this [file](https://github.com/neovim/neovim/blob/master/runtime/lua/vim/lsp/sync.lua)...

The source of this issue has been identified and fixed. Anyone interested can build #123 to test; the description has been updated. @mhanberg The PR is ready for review.