| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Vim9: dereferences NULL pointer in check_type_is_value()
(Suyue Guo)
Solution: Verify that the pointer is not Null
fixes: #15540
closes: #15545
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: Vim9: confusing error with .= in compiled functions
Solution: Check in error condition, if .= was attempted and in that case
give a different error message.
closes: #12972
closes: #13066
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: Various typos.
Solution: Correct typos. (closes #11432)
|
|
Problem: Too many delete() calls in tests.
Solution: Use deferred delete where possible.
|
|
Problem: Various small issues.
Solution: Various small fixes.
|
|
Problem: Trying to declare g:variable gives confusing error.
Solution: Give a better error message. (closes #11108)
|
|
Problem: Common names in test files causes tests to be flaky.
Solution: Use more specific names.
|
|
Problem: Test with BufNewFile autocmd is flaky.
Solution: Use another file name.
|
|
Problem: Invalid memory access when compiling :unlet.
Solution: Don't read past the end of the line.
|
|
Problem: Invalid memory access when compiling :lockvar.
Solution: Don't read past the end of the line.
|
|
Problem: execute() does not use the "legacy" command modifier.
Solution: pass the command modifier in sticky_cmdmod_flags. (Kota Kato,
closes #10845)
|
|
Problem: Cannot specify a function name for :defcompile.
Solution: Implement a function name argument for :defcompile.
|
|
Problem: "eval 123" gives an error, "eval 'abc'" does not.
Solution: Also give an error when evaluating only a string. (closes #10434)
|
|
Problem: Vim9: no error for using an expression only at the script level
when followed by an empty line.
Solution: Do not check the line number but whether something follows.
(closes #10357)
|
|
Problem: Vim9: some lines not covered by tests.
Solution: Add a few more tests. Fix disassemble output.
|
|
Problem: Vim9: can use :unlockvar for const variable. (Ernie Rael)
Solution: Check whether the variable is a const.
|
|
Problem: Vim9: not all code is tested.
Solution: Add a few more tests.
|
|
Problem: Vim9: assignment not recognized in skipped block.
Solution: When skipping assume identifier exists. (closes #10059)
|
|
Problem: Mapping with escaped bar does not work in :def function. (Sergey
Vlasov)
Solution: Do not remove the backslash. (closes #10002)
|
|
Problem: Vim9: not enough test coverage for executing :def function.
Solution: Add a few more tests.
|
|
Problem: Vim9: not enough test coverage for executing :def function.
Solution: Add a few more tests. Fix inconsistencies.
|
|
Problem: In a :def function "put = expr" does not work.
Solution: Skip over white space. (closes #9936)
|
|
Problem: Test fails because of new error message.
Solution: Avoid the test fails.
|
|
Problem: Vim9: some code not covered by tests.
Solution: Add a few more tests. Remove dead code.
|
|
Problem: Vim9: some code not covered by tests.
Solution: Add more tests. Avoid giving two errors. Remove dead code.
|
|
Problem: Some code lines not covered by tests.
Solution: Add a few more test cases. Fix getting more than one error for
invalid assignment.
|
|
Problem: Vim9: error message not tested, some code not tested.
Solution: Add a couple of test cases. Give an error for a command modifier
without a command.
|
|
Problem: sticky command modifiers are too sticky.
Solution: Do not apply command modifiers to a called function. (closes #9751)
|
|
Problem: Vim9: allowing use of "s:" leads to inconsistencies.
Solution: Disallow using "s:" in Vim9 script at the script level.
|
|
Problem: sticky command modifiers are too sticky.
Solution: Do not apply command modifiers to a sourced script. (closes #9751)
|
|
Problem: "legacy exe cmd" does not do what one would expect.
Solution: Apply the "legacy" and "vim9script" command modifiers to the
argument of ":execute".
|
|
Problem: :put does not work properly in compiled function. (John Beckett)
Solution: Adjust the direction when using line zero.
|
|
Problem: Vim9: not all code covered by tests.
Solution: Add a few more tests for corner cases. Fix hang when single quote
is missing.
|
|
Problem: Test fails.
Solution: Adjust the expected error number.
|
|
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: using "lockvar!" in :def function does not work.
Solution: Add "!" instead of "-1". (closes #9634)
|
|
Problem: Vim9: depth argument of :lockvar not parsed in :def function.
Solution: Parse the optional depth argument. (closes #9629)
Fix that locking doesn't work for a non-materialize list.
|
|
Problem: Vim9: some code lines not tested.
Solution: Add a few specific tests.
|
|
Problem: Vim9: not enough tests.
Solution: Add tests for :try/:catch and :redir. Add missing type check.
|
|
Problem: Vim9: inconsistent arguments for test functions.
Solution: When :def function and script have different arguments use a list
with two items instead of a separate function.
|
|
Problem: Vim9: using "legacy" before range does not work.
Solution: Skip over range before parsing command. (closes #9270)
|
|
Problem: Vim9: memory leak when compiling :elseif fails.
Solution: Cleanup ppconst.
|
|
Problem: Vim9: backtick expression expanded for :global.
Solution: Check the following command.
|
|
Problem: Vim9: backtick expression expanded when not desired.
Solution: Only expand a backtick expression for commands that expand their
argument. Remove a few outdated TODO comments.
|
|
Problem: Vim9: test fails with different error.
Solution: Correct the error number.
|
|
Problem: Vim9: "filter #pat# cmd" does not work.
Solution: Do not see #pat# as a comment.
|
|
Problem: Vim9: cannot use in :...do commands.
Solution: Add EX_EXPAND to the commands. (closes #9232)
|
|
Problem: Vim9: no error for an evironment variable by itself.
Solution: Give a "without effect" error. (closes #9166)
|
|
Problem: Vim9: no error for :lock or :unlock with unknown variable.
Solution: Give an error. (closes #9188)
|
