patch 9.1.1014: Vim9: variable not found in transitive import
Problem: Vim9: variable not found in transitive import
Solution: Allow nested import (Hirohito Higashi)
fixe: #16379
closes: #16440
Signed-off-by: Hirohito Higashi <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 2f64ba3..018f10d 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 9.1. Last change: 2025 Jan 12
+*options.txt* For Vim version 9.1. Last change: 2025 Jan 14
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -5582,6 +5582,7 @@
command recursion, see |E169|.
See also |:function|.
Also used for maximum depth of callback functions.
+ Also used for maximum depth of import. See |:import-cycle|.
*'maxmapdepth'* *'mmd'* *E223*
'maxmapdepth' 'mmd' number (default 1000)
diff --git a/runtime/doc/tags b/runtime/doc/tags
index 9310df8..05c2126 100644
--- a/runtime/doc/tags
+++ b/runtime/doc/tags
@@ -4148,6 +4148,7 @@
E1042 vim9.txt /*E1042*
E1043 vim9.txt /*E1043*
E1044 vim9.txt /*E1044*
+E1045 vim9.txt /*E1045*
E1047 vim9.txt /*E1047*
E1048 vim9.txt /*E1048*
E1049 vim9.txt /*E1049*
diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt
index a978ea3..05b451c 100644
--- a/runtime/doc/vim9.txt
+++ b/runtime/doc/vim9.txt
@@ -1,4 +1,4 @@
-*vim9.txt* For Vim version 9.1. Last change: 2024 Dec 23
+*vim9.txt* For Vim version 9.1. Last change: 2025 Jan 14
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -2051,13 +2051,14 @@
>
noremap ,a <ScriptCmd>:call s:that.OtherFunc()<CR>
<
- *:import-cycle*
-The `import` commands are executed when encountered. If script A imports
-script B, and B (directly or indirectly) imports A, this will be skipped over.
-At this point items in A after "import B" will not have been processed and
-defined yet. Therefore cyclic imports can exist and not result in an error
-directly, but may result in an error for items in A after "import B" not being
-defined. This does not apply to autoload imports, see the next section.
+ *:import-cycle* *E1045*
+The `import` commands are executed when encountered. It can be nested up to
+'maxfuncdepth' levels deep. If script A imports script B, and B (directly or
+indirectly) imports A, this will be skipped over. At this point items in A
+after "import B" will not have been processed and defined yet. Therefore
+cyclic imports can exist and not result in an error directly, but may result
+in an error for items in A after "import B" not being defined. This does not
+apply to autoload imports, see the next section.
Importing an autoload script ~