From 94525320365323f94cba93dce6926c3b1b062078 Mon Sep 17 00:00:00 2001 From: Björn Linse Date: Tue, 8 Jan 2019 20:37:35 +0100 Subject: API: don't directly call update_screen() in API functions There is no need to call update_screen() directly in an API function, mode input processing invokes update_screen() as needed. And if the API call is done in a context where redraw is disabled, then redraw is disabled for a reason. A lot of API functions are of equal semantical strength (nvim_call_function and nvim_execute_lua can also do whatever, nvim_command is not special), this inconsistency has no purpose. --- src/nvim/api/vim.c | 1 - 1 file changed, 1 deletion(-) (limited to 'src/nvim/api/vim.c') diff --git a/src/nvim/api/vim.c b/src/nvim/api/vim.c index 2a724a85ec..796923ffcb 100644 --- a/src/nvim/api/vim.c +++ b/src/nvim/api/vim.c @@ -75,7 +75,6 @@ void nvim_command(String command, Error *err) { try_start(); do_cmdline_cmd(command.data); - update_screen(VALID); try_end(err); } -- cgit