This would break compatibility with earlier versions of nvim. There is a deeper issue with gnvim's rpc client, which is that it doesn't respect this part of the API contract:
Future versions of Nvim may add new update kinds and may append new parameters
to existing update kinds. Clients must be prepared to ignore such extensions,
for forward-compatibility.
To fix this, gnvim's msgpack decoding needs to ignore extra values that it is not expecting to get. I'm not sure how this can be done since I haven't had a look at it.
I'm not ready to accept this pull request. We need to either
Wait for new nvim release and then pump gnvim's nvim version requirement
Fix the msgpack decoding
As a side note, most of the rpc types are generated straight from nvim's --api-info output. See the scripts/generate-bindings.sh script.
This would break compatibility with earlier versions of nvim. There is a deeper issue with gnvim's rpc client, which is that it doesn't respect this part of the API contract:
To fix this, gnvim's msgpack decoding needs to ignore extra values that it is not expecting to get. I'm not sure how this can be done since I haven't had a look at it.
I'm not ready to accept this pull request. We need to either
As a side note, most of the rpc types are generated straight from nvim's
--api-infooutput. See thescripts/generate-bindings.shscript.