summaryrefslogtreecommitdiff
path: root/src/errors.h
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2022-08-06 18:12:06 +0100
committerBram Moolenaar <Bram@vim.org>2022-08-06 18:12:06 +0100
commit3f74c0ab32de7ed17dd16d9b06f5455a0bb1c297 (patch)
tree9e625386219dc1f5503d7e9a6a7e3ae75a9d2e17 /src/errors.h
parentdb9b96d84491131460e5876fe21b9bbc58c73ed7 (diff)
downloadvim-git-3f74c0ab32de7ed17dd16d9b06f5455a0bb1c297.tar.gz
patch 9.0.0156: giving E1170 only in an expression is confusingv9.0.0156
Problem: Giving E1170 only in an expression is confusing. Solution: Give E1170 for any "#{ comment". (closes #10855)
Diffstat (limited to 'src/errors.h')
-rw-r--r--src/errors.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/errors.h b/src/errors.h
index 977abbf14..3b23c88ad 100644
--- a/src/errors.h
+++ b/src/errors.h
@@ -2984,8 +2984,8 @@ EXTERN char e_argument_already_declared_in_script_str[]
INIT(= N_("E1168: Argument already declared in the script: %s"));
EXTERN char e_expression_too_recursive_str[]
INIT(= N_("E1169: Expression too recursive: %s"));
-EXTERN char e_cannot_use_hash_curly_to_start_comment_in_an_expression[]
- INIT(= N_("E1170: Cannot use #{ to start a comment in an expression"));
+EXTERN char e_cannot_use_hash_curly_to_start_comment[]
+ INIT(= N_("E1170: Cannot use #{ to start a comment"));
EXTERN char e_missing_end_block[]
INIT(= N_("E1171: Missing } after inline function"));
EXTERN char e_cannot_use_default_values_in_lambda[]