From b544f3c81f1e6a50322855681ac266ffaa8e313c Mon Sep 17 00:00:00 2001 From: Bram Moolenaar Date: Thu, 23 Feb 2017 19:03:28 +0100 Subject: patch 8.0.0360: sometimes VimL is used instead of "Vim script" Problem: Sometimes VimL is used, which is confusing. Solution: Consistently use "Vim script". (Hirohito Higashi) --- src/if_py_both.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/if_py_both.h') diff --git a/src/if_py_both.h b/src/if_py_both.h index 4cd373402c..78c70e700b 100644 --- a/src/if_py_both.h +++ b/src/if_py_both.h @@ -582,9 +582,9 @@ VimTryStart(void) VimTryEnd(void) { --trylevel; - /* Without this it stops processing all subsequent VimL commands and - * generates strange error messages if I e.g. try calling Test() in a - * cycle */ + /* Without this it stops processing all subsequent Vim script commands and + * generates strange error messages if I e.g. try calling Test() in a cycle + */ did_emsg = FALSE; /* Keyboard interrupt should be preferred over anything else */ if (got_int) @@ -625,7 +625,7 @@ VimTryEnd(void) discard_current_exception(); return -1; } - /* Finally transform VimL exception to python one */ + /* Finally transform Vim script exception to python one */ else { PyErr_SetVim((char *)current_exception->value); -- cgit v1.2.3