Lines Matching refs:import

1346 					*vim9script* *vim9-export* *vim9-import*
1426 						*:import* *:imp* *E1094*
1428 	import EXPORTED_CONST from "thatscript.vim"
1429 	import MyClass from "myclass.vim"
1431 To import multiple items at the same time: >
1432 	import {someValue, MyClass} from "thatscript.vim"
1435 	import MyClass as ThatClass from "myclass.vim"
1436 	import {someValue, MyClass as ThatClass} from "myclass.vim"
1438 To import all exported items under a specific identifier: >
1439 	import * as That from 'thatscript.vim'
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
1452 The script name after `import` can be:
1459   "import" subdirectories of 'runtimepath' entries.  The name will usually be
1461   Note that "after/import" is not used.
1465 							*:import-cycle*
1466 The `import` commands are executed when encountered.  If that script (directly
1468 `import` won't be processed yet.  Therefore cyclic imports can exist, but may
1483 2. In the autoload script do the actual work.  You can import items from
1486 	import FilterFunc from "../import/someother.vim"
1500 <   This goes in .../import/someother.vim.
1508 If an `import` statement is used in legacy Vim script, the script-local "s:"
1536 - Extend a class with methods, using an import (like Dart)
1769 In Vim9 script a mechanism very similar to the JavaScript import and export
1778 - By using relative paths loading can be much faster for an import inside of a
1780 - Once an import has been used, it can be cached and loading it again can be
1790 - Completely disallow sourcing a Vim9 script, require using `:import`.  That
1793 Note that you can also use `:import` in legacy Vim script, see above.