Lines Matching refs:used
42 commonly used programming languages, such as JavaScript, TypeScript and Java.
50 The Vim9 script syntax and semantics are used in:
56 When using `:function` in a Vim9 script file the legacy syntax is used, with
98 - `:final` cannot be used as an abbreviation of `:finally`.
112 - Unless mentioned specifically, the highest |scriptversion| is used.
139 these can be used to start a fold.
141 In legacy Vim script # is also used for the alternate file name. In Vim9
158 - `:disassemble` is used for the function.
172 used for the command or inside a `:try` block), does not get a range passed
193 be used, type checking will then be done at runtime, like with legacy
215 The argument "_" (an underscore) can be used to ignore the argument. This is
229 variable the "g:" prefix must be used. For functions in an autoload script
241 When referring to a function and no "s:" or "g:" prefix is used, Vim will
249 Since a script-local function reference can be used without "s:" the name must
251 script "s:funcref" could be used, because it could not be referred to with
252 "funcref". In Vim9 script it can, therefore "s:Funcref" must be used to avoid
255 In all cases the function must be defined before used. That is when it is
329 used: >
358 In Vim9 script `:let` cannot be used. An existing variable is assigned to
415 used to repeat a `:substitute` command.
417 For an unpack assignment the underscore can be used to ignore a list item,
438 `:const` is used for making both the variable and the value a constant. Use
446 `:final` is used for making only the variable a constant, the value can be
495 Note that while variables need to be defined before they can be used,
504 A user defined function can be used as a function reference in an expression
569 No command can follow the "{", only a comment can be used there.
654 Like with legacy script '"\ ' is used. This is also needed when line
655 continuation is used without a backslash and a line starts with a bar: >
697 - "enddef" cannot be used at the start of a continuation line, it ends the
716 commands are used as an argument to another command, such as `windo`. In
717 those cases the line continuation with a backslash has to be used.
762 |curly-braces-names| cannot be used.
787 In case the key needs to be an expression, square brackets can be used, just
808 The 'ignorecase' option is not used for comparators that use strings.
888 result is a boolean. "!!" can be used to turn any value into boolean: >
899 can be used.
903 used, not "v:false" and "v:true" like in legacy script. "v:none" is not
904 changed, it is only used in JSON and has no equivalent in other languages.
926 Vim9 was designed to be closer to often used programming languages, but at the
948 expression or assignment, a few separators cannot be used when these commands
994 The `exists_compiled()` function can also be used for this.
1022 Patterns are used like 'magic' is set, unless explicitly overruled.
1023 The 'edcompatible' option value is not used.
1024 The 'gdefault' option value is not used.
1062 When the caller omits an argument the {value} is used.
1066 used. Syntax and type errors will be produced at that
1072 [!] is used as with `:function`. Note that
1102 Like `:disassemble` but with the instructions used for
1106 Like `:disassemble` but with the instructions used for
1125 For these the backtick expansion can be used. Example: >
1131 Or a script variable can be used: >
1186 These types can be used in declarations, but no simple value will actually
1190 efficient implementation is used that avoids allocating lot of small pieces of
1232 And classes and interfaces can be used as types: >
1288 If the values all have the same type, that type is used for the list or
1289 dictionary. If there is a mix of types, the "any" type is used. >
1319 before, if the value used matches the expected type. There will sometimes be
1373 In Vim9 script the global "g:" namespace can still be used as before. And the
1422 `:export` can only be used in Vim9 script, at the script level.
1446 `:import` can also be used in legacy Vim script. The imported items still
1449 `:import` can not be used in a function. Imported items are intended to exist
1457 will rarely be used.
1461 Note that "after/import" is not used.
1463 Once a vim9 script file has been imported, the result is cached and used the
1508 If an `import` statement is used in legacy Vim script, the script-local "s:"
1509 namespace will be used for the imported item, even when "s:" is not specified.
1594 number" instruction can be used, which is faster. The error can be given at
1599 is easy to understand and widely used. The type names are what were used in
1626 is accidentally used you are very likely to get an error message.
1632 different from what they are used to. To reduce this complaint popular
1633 languages are used as an example. At the same time, we do not want to abandon
1675 are used. That is different, thus it's good to use a different command:
1676 `:var`. This is used in many languages. The semantics might be slightly
1682 immutable we decided to use that. And then `:const` can be used for making
1683 both immutable. This was also used in legacy Vim script and the meaning is
1715 The first is more familiar for anyone used to C or Java. The second one
1740 used, e.g. with the `:if` command and the `||` operator, only boolean-like
1780 - Once an import has been used, it can be cached and loading it again can be
1785 globally can be used, not the exported items. Alternatives considered:
1798 Functions are compiled when called or when `:defcompile` is used. Why not
1824 these interfaces have never become widely used, for various reasons. When