| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Inconsistent capitalization in error messages.
Solution: Make capitalization consistent. (Doug Kearns)
|
|
Problem: String interpolation only works in heredoc.
Solution: Support interpolated strings. Use syntax for heredoc consistent
with strings, similar to C#. (closes #10327)
|
|
Problem: Accessing freed memory in test without the +channel feature.
(Dominique Pellé)
Solution: Do not generted PUSHCHANNEL or PUSHJOB if they are not
implemented. (closes #10350)
|
|
Problem: It is not easy to restore saved mappings.
Solution: Make mapset() accept a dict argument. (Ernie Rael, closes #10295)
|
|
Problem: Crash when using a number for lambda name.
Solution: Check the type of the lambda reference.
|
|
Problem: Unused code.
Solution: Remove code and add #ifdefs. (Dominique Pellé, closes #10136)
|
|
Problem: Cannot use expand() to get the script name.
Solution: Support expand('<script>'). (closes #10121)
|
|
Problem: New regexp engine does not give an error for "\%v".
Solution: Check for a value argument. (issue #10079)
|
|
Problem: "import autoload" does not check the file name.
Solution: Give an error if the file is not readable. (closes #10049)
|
|
Problem: Error for redefining a script item may be confusing.
Solution: Put quotes around the name.
|
|
Problem: Useless code handling a type declaration.
Solution: Remove the code and give an error.
|
|
Problem: A nested function (closure) is compiled for debugging without
context.
Solution: Check if a nested function is marked for debugging before
compiling it. Give an error when trying to compile a closure
without its context. (closes #9951)
|
|
Problem: Build failure without the +eval feature.
Solution: Move error message outside of #ifdef.
|
|
Problem: Old subsitute syntax is still supported.
Solution: Disallow using backslash after ":s" in Vim9 script.
|
|
Problem: Vim9: some flow commands can be shortened.
Solution: Also require using the full name for ":return", ":enddef",
":continue", ":export" and ":import".
|
|
Problem: Vim9: shortening commands leads to confusing script.
Solution: In Vim9 script require at least ":cont" for ":continue", "const"
instead of "cons", "break" instead of "brea", "catch" instead of
"cat", "else" instead of "el" "elseif" instead of "elsei" "endfor"
instead of "endfo" "endif" instead of "en" "endtry" instead of
"endt", "finally" instead of "fina", "throw" instead of "th",
"while" instead of "wh".
|
|
Problem: Vim9: can declare a variable with ":va".
Solution: Disallow using ":va", require using ":var".
|
|
Problem: "pattern not found" for :global is not an error message.
Solution: In Vim9 script make this an actual error, so that try/catch can be
used as expected.
|
|
Problem: Vim9: outdated "autocmd nested" still works.
Solution: Do not accept the :autocmd argument "nested" without "++" in Vim9
script.
|
|
Problem: Vim9: can declare a global variable on the command line.
Solution: Disallow declaring a variable on the command line. (closes #9881)
|
|
Problem: Vim9: wrong error for defining dict function.
Solution: Explicitly check for trying to define a dict function.
(closes 9827)
|
|
Problem: Vim9: some code not covered by tests.
Solution: Add a few more tests. Correct error message. Allow unlet on dict
with a number key.
|
|
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: Cannot build tiny version.
Solution: Adjust #ifdefs.
|
|
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: Vim9: can create a script variable from a legacy function.
Solution: Disallow creating a script variable from a function.
|
|
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: script-local function name can start with "_".
Solution: Check for leading capital after "s:". Correct error message.
|
|
Problem: MS-Windows: Vim exits when Python 3 initialisation fails.
Solution: Hook into the exit() function to recover from the failure.
(Ken Takata, closes #9710)
|
|
Problem: Error number used twice.
Solution: Renumber of of the errors.
|
|
Problem: Vim9: can use old style autoload function name.
Solution: Give an error for old style autoload function name.
|
|
Problem: One error message not in errors.h. (Antonio Colombo)
Solution: Move the message and rename.
|
|
Problem: Error for using flatten() in Vim9 script is unclear.
Solution: Add a remark to use flattennew().
|
|
Problem: test_garbagecollect_now() does not check v:testing as documented.
Solution: Give an error if v:testing is not set.
|
|
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: Condition with many "(" causes a crash.
Solution: Limit recursion to 1000.
|
|
Problem: Vim9: can use an autoload name in normal script.
Solution: Disallow using an autoload name.
|
|
Problem: Vim9: error message for old style import.
Solution: Use another error message. Add a test.
|
|
Problem: E464 does not always include the offending command.
Solution: Add another error message with "%s". (closes #9564)
|
|
Problem: Vim9: the "autoload" argument of ":vim9script" is not useful.
Solution: Remove the argument. (closes #9555)
|
|
Problem: Cannot use a method with a complex expression.
Solution: Evaluate the expression after "->" and use the result.
|
|
Problem: Translation related comment in the wrong place.
Solution: Move it back with the text. (Ken Takata, closes #9537)
|
|
Problem: Vim9: need to prefix every item in an autoload script.
Solution: First step in supporting "vim9script autoload" and "import
autoload".
|
|
Problem: Depending on the build features error messages are unused.
Solution: Add #ifdefs. (Dominique Pellé, closes #9493)
|
|
Problem: Some error messages not in the right place.
Solution: Adjust the errors file. Fix typo.
|
|
Problem: Vim9: no error when importing the same script twice.
Solution: Give an error, unless it is a reload.
|
|
Problem: Error for import not ending in .vim does not work for .vimrc.
Solution: Check that .vim is the end. (closes #9484)
|
|
Problem: Vim9: import mechanism is too complicated.
Solution: Do not use the Javascript mechanism but a much simpler one.
|
|
Problem: Build failure with tiny features. (Tony Mechelynck)
Solution: Adjust #ifdefs.
|
