| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Comment inside an expression in lambda ignores the rest of the
expression.
Solution: Truncate the line at the comment. (closes #10367)
|
|
Problem: Expression in command block does not look after NL when command is
typed.
Solution: Skip over NL also when not in a script. (closes #10358)
|
|
Problem: String interpolation only works in heredoc.
Solution: Support interpolated strings. Use syntax for heredoc consistent
with strings, similar to C#. (closes #10327)
|
|
Problem: Expression in command block does not look after NL.
Solution: Skip over NL to check what follows. (closes #10358)
|
|
Problem: Crash when using uninitialized function pointer.
Solution: Check for NULL pointer. (closes #10319, closes #10319)
|
|
Problem: Setting ufunc to NULL twice.
Solution: Set ufunc to NULL in find_exported(). (closes #19275)
|
|
Problem: Crash when imported autoload script was deleted.
Solution: Initialize local variable. (closes #10274) Give a more meaningful
error message.
|
|
Problem: Crash when using a number for lambda name.
Solution: Check the type of the lambda reference.
|
|
Problem: Cannot use <SID>FuncRef in completion spec.
Solution: Dereference a function name in another way. (closes #10197)
|
|
Problem: Error from setting an option is silently ignored.
Solution: Handle option value errors better. Fix uses of N_().
|
|
Problem: getcharpos() may change a mark position.
Solution: Copy the mark position. (closes #10148)
|
|
Problem: Vim9: can use :unlockvar for const variable. (Ernie Rael)
Solution: Check whether the variable is a const.
|
|
Problem: No error for using out of range list index.
Solution: Check list index at script level like in compiled function.
(closes #10051)
|
|
Problem: Errors for functions are sometimes hard to read.
Solution: Use printable_func_name() in more places.
|
|
Problem: Vim9: Crash with :execute and :finish. (Sergey Vlasov)
Solution: Check for NULL. (closes #10011)
|
|
Problem: Need to write script to a file to be able to source them.
Solution: Make ":source" use lines from the current buffer. (Yegappan
Lakshmanan et al., closes #9967)
|
|
Problem: Cannot index the g: dictionary.
Solution: Recognize using "g:[key]". (closes #9969)
|
|
Problem: Error for using autoload function in custom completion.
Solution: Do not check for errors when using an autoload function.
(closes #9962)
|
|
Problem: Useless code handling a type declaration.
Solution: Remove the code and give an error.
|
|
Problem: No warning when an autoload script for completion function has an
error.
Solution: Do not ignore errors when a function name is given with a dot or
'#' character. (closes #9958)
|
|
Problem: Vim9: test for profiling still fails.
Solution: Update flags for profiling and breakpoints when obtaining the
compile type. Do not set the FC_CLOSURE flag for a toplevel
function.
|
|
Problem: Test fails without the +job or +channel feature. (Dominique Pellé)
Solution: Adjust #ifdefs. Pass on skip flag. (closes #9942)
|
|
Problem: Line number for error is off by one.
Solution: Remember the line number of the comparison. (closes #9923)
|
|
Problem: Vim9: cannot set variables to a null value.
Solution: Add null_list, null_job, etc.
|
|
Problem: ctx_imports is not used.
Solution: Delete ctx_imports. Add missing dependency.
|
|
Problem: Calling in_vim9script() multiple times.
Solution: Call it once and keep the result.
|
|
Problem: Vim9: allowing use of "s:" leads to inconsistencies.
Solution: Disallow using "s:" in Vim9 script at the script level.
|
|
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: cstack not always passed to where it is needed.
Solution: Pass ctack through functions.
|
|
Problem: Vim9: crash when using funcref with closure.
Solution: Keep a reference to the funcref that has the outer context.
(closes #9716)
|
|
Problem: Various comment and indent mistakes, returning wrong zero.
Solution: Fix the mistakes. Return NULL instead of FAIL.
|
|
Problem: Vim9: strict type checking after copy() and deepcopy().
Solution: Allow type to change after making a copy. (closes #9644)
|
|
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: Theoretical computation overflow.
Solution: Perform multiplication in a wider type. (closes #9657)
|
|
Problem: Filter-map test fails.
Solution: Only reject number argument in Vim9 script.
|
|
Problem: Vim9: no error when using a number for map() second argument
Solution: Disallow number to string conversion. (closes #9630)
|
|
Problem: Long/int compiler warnings; function arguments swapped.
Solution: Add type casts. Swap arguments. (Ken Takata, closes #9632)
|
|
Problem: Recursion test fails with MSVC.
Solution: Use a smaller limit for MSVC.
|
|
Problem: Condition with many "(" causes a crash.
Solution: Limit recursion to 1000.
|
|
Problem: 'foldtext' is evaluated in the current script context.
Solution: Use the script context where the option was set.
|
|
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: Confusing error when using name of import for a function.
Solution: Pass a flag to trans_function_name().
|
|
Problem: Crash when method cannot be found. (Christian J. Robinson)
Solution: Don't mix up pointer names.
|
|
Problem: Completion tests fail.
Solution: Disable error messages while dereferencing the function name.
|
|
Problem: Complete function cannot be import.Name.
Solution: Dereference the function name if needed. Also: do not see
"import.Name" as a builtin function. (closes #9541)
|
|
Problem: Vim9: wrong white space error after using imported item.
Solution: Don't skip over white space. (closes #9544)
|
|
Problem: Cannot use a method with a complex expression.
Solution: Evaluate the expression after "->" and use the result.
|
|
Problem: Coverity warns for using NULL pointer.
Solution: Check "evalarg" is not NULL. Skip errors when "verbose" is false.
|
|
Problem: Vim9: import cannot be used after method.
Solution: Recognize an imported function name. (closes #9496)
|
