patch 8.2.0103: using null object with execute() has strange effects Commit: https://github.com/vim/vim/commit/e2a8f0773e91685843c062b1e48259712d5f2213 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Jan 8 19:32:18 2020 +0100 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.

--- a/src/evalfunc.c
+++ b/src/evalfunc.c
@@ -2015,6 +2015,12 @@ execute_common(typval_T *argvars, typval
 	    return;
 	++list->lv_refcount;
     }
+    else if (argvars[arg_off].v_type == VAR_JOB
+	    || argvars[arg_off].v_type == VAR_CHANNEL)
+    {
+	emsg(_(e_inval_string));
+	return;
+    }
     else
     {
 	cmd = tv_get_string_chk(&argvars[arg_off]);