Mercurial > vim
diff runtime/doc/usr_41.txt @ 29290:dc4de65a7fb7
Update runtime files
Commit: https://github.com/vim/vim/commit/8a3b805c6c9cae341d560df9c3567ebbe42a7404
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Jun 26 12:21:15 2022 +0100
Update runtime files
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sun, 26 Jun 2022 13:30:04 +0200 |
parents | 0fdf36de4018 |
children | f8116058ca76 |
line wrap: on
line diff
--- a/runtime/doc/usr_41.txt +++ b/runtime/doc/usr_41.txt @@ -322,7 +322,7 @@ want to give the variable a value yet, y If you make a mistake and try to assign the wrong type of value you'll get an error: > - + age = "Peter" < E1012: Type mismatch; expected number but got string ~ @@ -638,7 +638,7 @@ Make sure that the argument for `normal` Vim will run into the end of the argument and silently abort the command. For example, if you start the delete operator, you must give the movement command also. This works: > - + normal d$ This does nothing: > @@ -1567,7 +1567,7 @@ to "funcref". Example: > def Wrong(): string return 'Wrong!' enddef - + var Afunc = g:result == 1 ? Right : Wrong echo Afunc() < Wrong! ~ @@ -1815,7 +1815,7 @@ is ignored, except for commands that don examples below. A comment can start on any character position on the line, but not when it is part of the command, e.g. inside a string. -The character " (the double quote mark) starts a comment in legacy script. +The character " (the double quote mark) starts a comment in legacy script. This involves some cleverness to make sure double quoted strings are not recognized as comments (just one reason to prefer |Vim9| script).