| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Function implementing :substitute has unexpected name.
Solution: Rename from do_sub() to ex_substitute().
|
|
Problem: Vim9: always converting to string for ".." leads to mistakes.
Solution: Only automatically convert simple types.
|
|
Problem: The Mac GUI implementation is outdated and probably doesn't even
work.
Solution: Remove the Mac GUI code. The MacVim project provides the
supported Vim GUI version.
|
|
Problem: Vim9: type of list and dict only depends on first item.
Solution: Use all items to decide about the type.
|
|
Problem: Vim9: vim9compile.c is getting too big.
Solution: Split off type code to vim9type.c.
|
|
Problem: Cannot jump to the last used tabpage.
Solution: Add g<Tab> and tabpagnr('#'). (Yegappan Lakshmanan, closes #6661,
neovim #11626)
|
|
Problem: Vim9: may find imported item in wrong script.
Solution: When looking up script-local function use the embedded script ID.
(issue #6644)
|
|
Problem: Vim9: no error if declaring a funcref with a lower case letter.
Solution: Check the name after the type is inferred. Fix confusing name.
|
|
Problem: Vim9: no error for missing white space around operator.
Solution: Check for white space. (closes #6618)
|
|
Problem: CTRL-C in the GUI doesn't interrupt. (Sergey Vlasov)
Solution: Recognize "C" with CTRL modifier as CTRL-C. (issue #6565)
|
|
Problem: Vim9: memory leak when using nested global function.
Solution: Delete the function when deleting the instruction. Disable test
that still causes a leak.
|
|
Problem: Vim9: cannot define global function inside :def function.
Solution: Assign to global variable instead of local. (closes #6584)
|
|
Problem: Vim9: invalid operators only rejected in :def function.
Solution: Also reject them at script level. (closes #6564)
|
|
Problem: Vim9: accidentally using "x" causes Vim to exit.
Solution: Disallow using ":x" or "xit" in Vim9 script. (closes #6399)
|
|
Problem: Checking for first character of dict key is inconsistent.
Solution: Add eval_isdictc(). (closes #6546)
|
|
Problem: Vim9: optional argument type not parsed properly.
Solution: Skip over the "?". (issue #6507)
|
|
Problem: When a test fails it's often not easy to see what the call stack
is.
Solution: Add more entries from the call stack in the exception message.
|
|
Problem: Ex command error cannot contain an argument.
Solution: Add ex_errmsg() and translate earlier. Use e_trailing_arg where
possible.
|
|
Problem: Vim9: type not checked if declaration also assigns value.
Solution: Check the type. (issue #6507)
|
|
Problem: Language and locale code spread out.
Solution: Move relevant code to src/locale.c. (Yegappan Lakshmanan,
closes #6509)
|
|
Problem: src/ex_cmds.c file is too big.
Solution: Move help related code to src/help.c. (Yegappan Lakshmanan,
closes #6506)
|
|
Problem: Cannot use a lambda with quickfix functions.
Solution: Add support for lambda. (Yegappan Lakshmanan, closes #6499)
|
|
Problem: Vim9: warning for pointer usage, test failure undetected.
Solution: Fix pointer indirection. Give error when executing function
failed for any reason. Fix instruction names.
|
|
Problem: Vim9: cannot have a comment or empty line halfway a list at script
level.
Solution: Skip more than one line if needed.
|
|
Problem: Vim9: no error if calling a function with wrong argument type.
Solution: Check types of arguments. (closes #6469)
|
|
Problem: Changing 'completepopup' after opening a popup has no effect. (Jay
Sitter)
Solution: Close the popup when the options are changed. (closes #6471)
|
|
Problem: MS-Windows: GUI code can be cleaned up.
Solution: Do a bit of cleaning up. (Ken Takata, closes #6465)
|
|
Problem: Build error without the eval feature.
Solution: Declare starts_with_colon. Make function local.
|
|
Problem: Scrollbars not flush against the window edges when maximised.
Solution: Add padding. (Ken Takata, closes #5602, closes #6466)
|
|
Problem: Vim9: allowing both quoted and # comments is confusing.
Solution: Only support # comments in Vim9 script.
|
|
Problem: Vim9: not enough type checking in Vim9 script.
Solution: Use same type checking as in a :def function.
|
|
Problem: Text cleared by checking terminal properties not redrawn. (Alexey
Radkov)
Solution: Mark the screen characters as invalid. (closes #6422)
|
|
Problem: Vim9: using freed memory.
Solution: Put pointer back in evalarg instead of freeing it.
|
|
Problem: Vim9: memory leak in allocated types.
Solution: Free the type pointers.
|
|
Problem: Vim9: cannot handle line break inside lambda.
Solution: Pass the compilation context through. (closes #6407, closes #6409)
|
|
Problem: Vim9: crash when using imported function.
Solution: Check for a function type. Set the script context when calling a
function. (closes #6412)
|
|
Problem: Warning for using int instead of size_t.
Solution: Change "len" argument to size_t. (Mike Williams)
|
|
Problem: Vim9: modifiers not cleared after compiling function.
Solution: Clear command modifiers. (closes #6396)
|
|
Problem: Vim9: double quote can be a string or a comment.
Solution: Only support comments starting with # to avoid confusion.
|
|
Problem: Vim9: no line break allowed in :import command.
Solution: Skip over line breaks.
|
|
Problem: Inconsistent naming of get_list_tv() and eval_dict().
Solution: Rename get_list_tv() to eval_list(). Similarly for eval_number(),
eval_string(), eval_lit_string() and a few others.
|
|
Problem: Vim9: line continuation does not work in function arguments.
Solution: Pass "evalarg" to get_func_tv(). Fix seeing double quoted string
as comment.
|
|
Problem: Vim9: no line break allowed in a for loop.
Solution: Skip line breaks in for command.
|
|
Problem: Vim9: no line break allowed in a while loop.
Solution: Update stored loop lines when finding line breaks.
|
|
Problem: Highlight and match functionality together in one file.
Solution: Move match functionality to a separate file. (Yegappan Lakshmanan,
closes #6352)
|
|
Problem: Vim9: no line break allowed in :if expression.
Solution: Skip linebreak.
|
|
Problem: Vim9: no line break allowed after some operators.
Solution: Skip a line break after the operator. Add
eval_may_get_next_line() to simplify checking for a line break.
|
|
Problem: Vim9: no line break allowed inside a lambda.
Solution: Handle line break inside a lambda in Vim9 script.
|
|
Problem: Vim9: no line break allowed inside a dict.
Solution: Handle line break inside a dict in Vim9 script.
|
|
Problem: Expression "!expr->func()" does not work.
Solution: Apply plus and minus earlier. (closes #6348)
|
