Mercurial > vim
diff src/errors.h @ 29631:9d54c8e6c682 v9.0.0156
patch 9.0.0156: giving E1170 only in an expression is confusing
Commit: https://github.com/vim/vim/commit/3f74c0ab32de7ed17dd16d9b06f5455a0bb1c297
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Aug 6 18:12:06 2022 +0100
patch 9.0.0156: giving E1170 only in an expression is confusing
Problem: Giving E1170 only in an expression is confusing.
Solution: Give E1170 for any "#{ comment". (closes https://github.com/vim/vim/issues/10855)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sat, 06 Aug 2022 19:15:03 +0200 |
| parents | 842690841d50 |
| children | c1c599a367d4 |
line wrap: on
line diff
--- a/src/errors.h +++ b/src/errors.h @@ -2984,8 +2984,8 @@ EXTERN char e_argument_already_declared_ 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[]