oberblastmeister

Its okay, I was working on a larger pr after I submitted this one by I lost interest. However, I do think it is very nice because then all functions...

The type signature can be generic because we can use `Value` internally. `Value` implements `Serialize` and `Deserialize` when `with-serde` feature is enabled for `rmpv`.

Also if you don't want to explicitly do `deserialize` and idea is to use associated types like this ```rust trait Handler { type RequestArg: DeserializeOwned; type NotifyArg: DeserializeOwned; } ```

> But that still exposes Vec, and seemingly by necessity, because how else would one handle the different possible values that could be passed into an rpcnotify(...) call from the...

> My point here was more about how to avoid exposing rmpv::Value in handle_notify etc. Ok that makes sense.

This would allow integration with delta as described in this [issue](https://github.com/dandavison/delta/issues/535)

just curious, why must it be a vimscript implementation?

I think both implementations are okay on the outside and expr mappings definately work with lua. However, lua is trying to be a first class citizen in neovim and since...

I don't think it makes sense to do that. There are many good plugins but I don't think that they should be moved to nvim-lua just because. I think it...

this issue has happened to me. The issue is that the virtual text sometimes will not be in sync because we only update virtual text for the lines that we...