FUNC_API_REMOTE_ONLY in Lua/Vimscript #28437
Labels
Milestone
Comments
justinmk
added a commit
to justinmk/neovim
that referenced
this issue
Apr 22, 2024
TODO: FUNC_API_REMOTE_ONLY APIs such as `nvim_ui_*` cannot (yet) be used in `nvim_exec_lua`. We can change FUNC_API_REMOTE_ONLY to allow Vimscript/Lua to pass an explicit `channel_id`. neovim#28437
justinmk
added a commit
that referenced
this issue
Apr 22, 2024
TODO: FUNC_API_REMOTE_ONLY APIs such as `nvim_ui_*` cannot (yet) be used in `nvim_exec_lua`. We can change FUNC_API_REMOTE_ONLY to allow Vimscript/Lua to pass an explicit `channel_id`. #28437
RandomChugokujin
pushed a commit
to RandomChugokujin/neovim
that referenced
this issue
Apr 24, 2024
TODO: FUNC_API_REMOTE_ONLY APIs such as `nvim_ui_*` cannot (yet) be used in `nvim_exec_lua`. We can change FUNC_API_REMOTE_ONLY to allow Vimscript/Lua to pass an explicit `channel_id`. neovim#28437
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
FUNC_API_REMOTE_ONLY marks functions that require a channel id and these functions currently aren't usable from Lua/vimscript.
Expected behavior
Rename FUNC_API_REMOTE_ONLY to FUNC_API_CHAN_REQUIRED so that Lua/Vimscript can pass an explicit channel id. This allows those functions to be batched via
nvim_exec_lua, and removes the last remaining use case of nvim_call_atomic. #28433The text was updated successfully, but these errors were encountered: