| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Need a new release
Solution: Release Vim 9.1
Signed-off-by: Christian Brabandt <cb@256bit.org>
|
|
Problem: Vim9: no support for bitwise operators in lambda funcs
Solution: move "evaluate" assignment a bit up in order to decide
to perform bitwise operations
closes: #13342
closes: #13345
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
|
|
Problem: Cannot use positional arguments for printf()
Solution: Support positional arguments in string formatting
closes: #12140
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Christ van Willegen <cvwillegen@gmail.com>
|
|
Problem: Users may not know what to do with an internal error.
Solution: Add a translated message with instructions.
|
|
Problem: Passing -1 for bool is not always rejected.
Solution: Check for error in a better way. (closes #12358)
|
|
Problem: Some functions give two error messages.
Solution: Do not give a second error message. (closes #12352)
|
|
Problem: The falsy operator is not tested properly.
Solution: Add a few more test cases. (closes #12319)
|
|
Problem: Using uninitialized memory when argument is missing.
Solution: Check there are sufficient arguments before the base.
(closes #12302)
|
|
Problem: Various typos.
Solution: Correct typos. (closes #11432)
|
|
Problem: Crash when trying to divice the largest negative number by -1.
Solution: Handle this case specifically.
|
|
Problem: Manually deleting test temp files.
Solution: Add the 'D' flag to writefile().
|
|
Problem: No good reason to build without the float feature.
Solution: Remove configure check for float and "#ifdef FEAT_FLOAT".
|
|
Problem: Checks for Dictionary argument often give a vague error message.
Solution: Give a useful error message. (Yegappan Lakshmanan, closes #11009)
|
|
Problem: has() is not strict about parsing the patch version.
Solution: Check the version more strictly. (Ken Takata, closes #10752)
|
|
Problem: has('patch-xxx') returns true.
Solution: Check for digit. (closes #10751)
|
|
Problem: Right shift on negative number does not work as documented.
Solution: Use a uvarnumber_T type cast.
|
|
Problem: Cannot do bitwise shifts.
Solution: Add the >> and << operators. (Yegappan Lakshmanan, closes #8457)
|
|
Problem: Interpolated string expression requires escaping.
Solution: Do not require escaping in the expression.
|
|
Problem: String interpolation only works in heredoc.
Solution: Support interpolated strings. Use syntax for heredoc consistent
with strings, similar to C#. (closes #10327)
|
|
Problem: Making comparison with null work changes legacy behavior.
Solution: Only use the better comparison in Vim9 script. (closes #9910)
|
|
Problem: Vim9: cannot set variables to a null value.
Solution: Add null_list, null_job, etc.
|
|
Problem: Operator name spelled wrong.
Solution: Change trinary to ternary. (Goc Dundar, closes #9850)
|
|
Problem: Expression test fails.
Solution: Make the test work with latest Vim9 syntax.
|
|
Problem: Vim9: some tests fail.
Solution: Fix the tests, mostly by removing "s:".
|
|
Problem: The EBCDIC support is outdated.
Solution: Remove the EBCDIC support.
|
|
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: Cannot use a script-local function for 'foldtext'.
Solution: Expand "s:" and "<SID>". (Yegappan Lakshmanan, closes #9411)
|
|
Problem: Duplicate code for translating script-local function name.
Solution: Move the code to get_scriptlocal_funcname(). (Yegappan Lakshmanan,
closes #9393)
|
|
Problem: Vim9: not enough tests.
Solution: Run more expression tests also with Vim9. Fix an uncovered
problem.
|
|
Problem: Cannot pass a lambda name to function() or funcref(). (Yegappan
Lakshmanan)
Solution: Handle a lambda name differently.
|
|
Problem: Using %S in printf() does not work correctly.
Solution: Fix the problem and add more tests. (closes #9208)
|
|
Problem: Printf() with %S does not handle multi-byte correctly.
Solution: Count cells instead of bytes. (closes #9169, closes #7486)
|
|
Problem: Crash when using NULL string for funcref().
Solution: Check for NULL argument. (issue #8260)
|
|
Problem: Various pieces of code not covered by tests.
Solution: Add a few more tests. (Yegappan Lakshmanan, closes #8255)
|
|
Problem: Check for features implemented with "if".
Solution: Use the Check commands. (Ken Takata, closes #7383)
|
|
Problem: Vim9: trinary operator condition is too permissive.
Solution: Use tv_get_bool_chk().
|
|
Problem: No falsy Coalescing operator.
Solution: Add the "??" operator. Fix mistake with function argument count.
|
|
Problem: Cannot put space between function name and paren.
Solution: Allow this for backwards compatibility.
|
|
Problem: Error for white space after expression in assignment.
Solution: Skip over white space. (closes #6617)
|
|
Problem: assert_fails() checks the last error message.
Solution: Check the first error, it is more relevant. Fix all the tests
that rely on the old behavior.
|
|
Problem: Expression "!expr->func()" does not work.
Solution: Apply plus and minus earlier. (closes #6348)
|
|
Problem: Insufficient testing for invalid function arguments.
Solution: Add more tests. (Yegappan Lakshmanan, closes #5988)
|
|
Problem: Crash with null partial and blob.
Solution: Check for NULL pointer. Add more tests. (Yegappan Lakshmanan,
closes #5984)
|
|
Problem: Crash when using null partial in filter().
Solution: Fix crash. Add more tests. (Yegappan Lakshmanan, closes #5976)
|
|
Problem: Null dict is not handled like an empty dict.
Solution: Fix the code and add tests. (Yegappan Lakshmanan, closes #5968)
|
|
Problem: Some tests are still old style.
Solution: Convert to new style tests. (Yegappan Lakshmanan, closes #5957)
|
|
Problem: Some errors are not covered by tests.
Solution: Add a few more tests. (Dominique Pelle, closes #5920)
|
|
Problem: Regexp and other code not tested.
Solution: Add more tests. (Yegappan Lakshmanan, closes #5904)
|
|
Problem: Several errors are not tested for.
Solution: Add tests. (Yegappan Lakshmanan, closes #5892)
|
|
Problem: Various functions not properly tested.
Solution: Add more tests, especially for failures. (Yegappan Lakshmanan,
closes #5843)
|
