Justin M. Keyes
Justin M. Keyes
> The latter looks worse to me since the logic for `field2` is now fragmented. Yeah, good point. Ok, let's align on https://github.com/neovim/neovim/issues/32287#issuecomment-2835155023
The remote plugin concept will be removed, because it's not needed if pynvim just provides a `set_handler` function. See https://github.com/neovim/pynvim/issues/567 @b0o any chance you can implement set_handler in pynvim?
> According to the results, the bug was fixed in commit [db3b856](https://github.com/neovim/neovim/commit/db3b85677928e4157d459aebb21a673a8bc84f28) . That doesn't seem right...
@GreatGatsby102 create a new issue.
Should be fixed in Nvim 0.11.4 by https://github.com/neovim/neovim/pull/35307
There was a request(s) for this in the issue tracker. Please link to it/them, and if there were tradeoffs mentioned, explain how this addresses the tradeoffs or why it should...
Example use-case: https://github.com/vscode-neovim/vscode-neovim/issues/1902
See https://github.com/neovim/neovim/pull/34318#discussion_r2144946570 The assert is only enabled for debug builds.
Maybe our treesitter C code can translate `UINT32_MAX` to `HUGE_VAL` before marshalling.