| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Cannot use import->Func() in lambda. (Israel Chauca Fuentes)
Solution: Adjust how an expression in a lambda is parsed. (closes #11042)
|
|
Problem: Common names in test files causes tests to be flaky.
Solution: Use more specific names.
|
|
Problem: Using common name in tests leads to flaky tests.
Solution: Rename files and directories to be more specific.
|
|
Problem: It is not easy to get information about a script.
Solution: Make getscriptinf() return the version. When selecting a specific
script return functions and variables. (Yegappan Lakshmanan,
closes #10991)
|
|
Problem: getscriptinfo() does not include the version. Cannot select
entries by script name.
Solution: Add the "version" item and the "name" argument. (Yegappan
Lakshmanan, closes #10962)
|
|
Problem: "->" in ":scriptnames" output not tested yet.
Solution: Add a check.
|
|
Problem: A symlink to an autoload script results in two entries in the list
of scripts, items expected in one are actually in the other.
Solution: Have one script item refer to the actually sourced one.
(closes #10960)
|
|
Problem: Cannot easily get the list of sourced scripts.
Solution: Add the getscriptinfo() function. (Yegappan Lakshmanan,
closes #10957)
|
|
Problem: Import test fails because 'diffexpr' isn't reset.
Solution: Reset 'diffexpr'.
|
|
Problem: Vim9: a few lines not covered by tests.
Solution: Add a few tests.
|
|
Problem: Crash when imported autoload script was deleted.
Solution: Initialize local variable. (closes #10274) Give a more meaningful
error message.
|
|
Problem: Various things no6 properly tested.
Solution: Add various test cases. (Yegappan Lakshmanan, closes #10259)
|
|
Problem: Cannot use <SID>FuncRef in completion spec.
Solution: Dereference a function name in another way. (closes #10197)
|
|
Problem: Mapping <SID>name.Func does not work for script in autoload
directory.
Solution: Use the # form for a script in the autoload directory.
(closes #10186)
|
|
Problem: Cannot use an imported function in a mapping.
Solution: Recognize <SID>name.Func.
|
|
Problem: Build failure without +postscript.
Solution: Use another error message.
|
|
Problem: Vim9: not all code is tested.
Solution: Add a few more tests.
|
|
Problem: Vim9: can't use items from "import autoload" with autoload
directory name.
Solution: Let sn_autoload_prefix overrule sn_import_autoload.
(closes #10054)
|
|
Problem: "import autoload" does not check the file name.
Solution: Give an error if the file is not readable. (closes #10049)
|
|
Problem: "import autoload" only works with using 'runtimepath'.
Solution: Also support a relative and absolute file name.
|
|
Problem: Test fails because of changed error message.
Solution: Update the expected error message
|
|
Problem: Using script-local function from the wrong script when using a
partial. (Yegappan Lakshmanan)
Solution: Include the script ID in the partial name.
|
|
Problem: Vim9: some code not covered by tests.
Solution: Add a few specific test cases.
|
|
Problem: Vim9: allowing use of "s:" leads to inconsistencies.
Solution: Disallow using "s:" in Vim9 script at the script level.
|
|
Problem: Vim9: no error if script imports itself.
Solution: Give an error when a script imports itself.
|
|
Problem: Vim9: cannot list autoload function.
Solution: Don't give an error for using # when listing a function.
(closes #9703)
|
|
Problem: Vim9: an import does not shadow a command modifier.
Solution: Do not accept a command modifier followed by a dot.
|
|
Problem: Vim9: can use old style autoload function name.
Solution: Give an error for old style autoload function name.
|
|
Problem: Vim9: can still use a global function without g: at the script
level.
Solution: Also check for g: at the script level. (issue #9637)
|
|
Problem: Vim9: finding global function without g: prefix but not finding
global variable is inconsistent.
Solution: Require using g: for a global function. Change the vim9.vim
script into a Vim9 script with exports. Fix that import in legacy
script does not work.
|
|
Problem: Vim9: cannot use a function from an autoload import directly.
Solution: Add the AUTOLOAD instruction to figure out at runtime.
(closes #9620)
|
|
Problem: partial in 'opfunc' cannot use an imported function.
Solution: Also expand the function name in a partial. (closes #9614)
|
|
Problem: Vim9: cannot export function that exists globally.
Solution: When checking if a function already exists only check for
script-local functions. (closes #9615)
|
|
Problem: Some tests do not clean up properly.
Solution: Delete created files. (Yegappan Lakshmanan, closes #9611)
|
|
Problem: Cannot use an import in the "expr" part of 'spellsuggest'.
Solution: Set the script context when evaluating "expr" of 'spellsuggest'.
|
|
Problem: Cannot use an import in 'charconvert'.
Solution: Set the script context when evaluating 'charconvert'. Also expand
script-local functions in 'charconvert'.
|
|
Problem: Cannot use an import in 'printexpr'.
Solution: Set the script context when evaluating 'printexpr'.
|
|
Problem: Cannot use an import in 'patchexpr'.
Solution: Set the script context when evaluating 'patchexpr'. Do not
require 'patchexpr' to return a bool, it was ignored anyway.
|
|
Problem: Cannot use an import in 'indentexpr'.
Solution: Set the script context when evaluating 'indentexpr'
|
|
Problem: Cannot use an import in 'includeexpr'.
Solution: Set the script context when evaluating 'includeexpr'
|
|
Problem: Cannot use an import in 'formatexpr'.
Solution: Set the script context when evaluating 'formatexpr'.
|
|
Problem: Vim9: cannot use an import in 'diffexpr'.
Solution: Set the script context when evaluating 'diffexpr'. Do not require
'diffexpr' to return a bool, it was ignored anyway.
|
|
Problem: 'foldtext' is evaluated in the current script context.
Solution: Use the script context where the option was set.
|
|
Problem: Vim9: autoload script not loaded after "vim9script noclear".
Solution: Check IMP_FLAGS_AUTOLOAD properly.
|
|
Problem: Vim9: cannot use imported function with call().
Solution: Translate the function name. (closes #9590)
|
|
Problem: Vim9: can use an autoload name in normal script.
Solution: Disallow using an autoload name.
|
|
Problem: Cannot use an import in 'foldexpr'.
Solution: Set the script context to where 'foldexpr' was set. (closes #9584)
Fix that the script context was not set for all buffers.
|
|
Problem: Cannot invoke option function using autoload import.
Solution: Expand the import to an autoload function name. (closes #9578)
|
|
Problem: Vim9: error message for old style import.
Solution: Use another error message. Add a test.
|
|
Problem: No error for omitting function name after autoload prefix.
Solution: Check for missing function name. (issue #9577)
|
