Lines Matching refs:legacy
56 When using `:function` in a Vim9 script file the legacy syntax is used, with
60 Vim9 script and legacy Vim script can be mixed. There is no requirement to
66 Useful when typing a command and in a legacy script or
69 :leg[acy] {cmd} *:leg* *:legacy*
70 Execute {cmd} using legacy script syntax and semantics. Only
73 with legacy expression syntax.
77 2. Differences from legacy Vim script *vim9-differences*
117 In legacy Vim script comments start with double quote. In Vim9 script
137 Do not start a comment with #{, it looks like the legacy dictionary literal
141 In legacy Vim script # is also used for the alternate file name. In Vim9
183 You can call a legacy dict function though: >
193 be used, type checking will then be done at runtime, like with legacy
250 start with an upper case letter even when using the "s:" prefix. In legacy
269 You can use an autoload function if needed, or call a legacy function and have
275 When loading a legacy Vim script a second time nothing is removed, the
517 In legacy script there can be confusion between using "->" for a method call
542 In legacy script a lambda could be called with any number of extra arguments,
654 Like with legacy script '"\ ' is used. This is also needed when line
813 In legacy script, when an error is encountered, Vim continues to execute
827 Example legacy script: >
848 Some values are different from legacy Vim script:
849 value legacy Vim script Vim9 script ~
903 used, not "v:false" and "v:true" like in legacy script. "v:none" is not
910 In legacy script this results in the character 0xc3 (an illegal byte), in Vim9
917 In legacy script "++var" and "--var" would be silently accepted and have no
927 same time tries to support the legacy Vim commands. Some compromises had to
931 -> legacy Vim: shifts the previous line to the right
935 %s/a/b legacy Vim: substitute on all lines
939 't legacy Vim: jump to mark t
1087 legacy script, then script-local variables must be accessed with the "s:"
1307 variable was declared in a legacy function.
1312 In legacy Vim script, where a number was expected, a string would be
1370 variables in legacy Vim script, but the "s:" is omitted. And they cannot be
1386 There is one way to use both legacy and Vim9 syntax in one script file: >
1389 " legacy script commands go here
1446 `:import` can also be used in legacy Vim script. The imported items still
1506 Import in legacy Vim script ~
1508 If an `import` statement is used in legacy Vim script, the script-local "s:"
1579 considered the best way to separate the legacy style code from Vim9 style code.
1582 "function" which clashes with legacy Vim script.
1605 Once decided that `:def` functions have different syntax than legacy functions,
1634 the well-known parts of legacy Vim script.
1640 legacy Vim script is dynamically typed and a lot of existing functionality
1657 goes against legacy Vim script and often leads to mistakes. For that reason
1683 both immutable. This was also used in legacy Vim script and the meaning is
1691 Since legacy and Vim9 script will be mixed and global variables will be
1764 A problem of legacy Vim script is that by default all functions and variables
1784 When sourcing a Vim9 script from a legacy script, only the items defined
1793 Note that you can also use `:import` in legacy Vim script, see above.