mirror of
https://github.com/neovim/neovim.git
synced 2025-10-17 07:16:09 +00:00
vim-patch:8.2.0103: using null object with execute() has strange effects
Problem: Using null object with execute() has strange effects.
Solution: Give an error message ofr Job and Channel.
e2a8f0773e
Co-authored-by: Bram Moolenaar <Bram@vim.org>
This commit is contained in:
@@ -998,6 +998,7 @@ EXTERN const char e_listarg[] INIT(= N_("E686: Argument of %s must be a List"));
|
||||
EXTERN const char e_unsupportedoption[] INIT(= N_("E519: Option not supported"));
|
||||
EXTERN const char e_fnametoolong[] INIT(= N_("E856: Filename too long"));
|
||||
EXTERN const char e_float_as_string[] INIT(= N_("E806: using Float as a String"));
|
||||
EXTERN const char e_inval_string[] INIT(= N_("E908: using an invalid value as a String"));
|
||||
EXTERN const char e_cannot_edit_other_buf[] INIT(= N_("E788: Not allowed to edit another buffer now"));
|
||||
|
||||
EXTERN const char e_cmdmap_err[] INIT(= N_("E5520: <Cmd> mapping must end with <CR>"));
|
||||
|
Reference in New Issue
Block a user