| Age | Commit message (Collapse) | Author |
|---|
|
Problem: A popup filter interferes with using :normal to move the cursor in
a popup.
Solution: Do not invoke the filter when ex_normal_busy is set.
|
|
Problem: Vim9: Cannot use "fina" for "finally". (Naruhiko Nishino)
Solution: Specifically check for "fina". (closes #7020)
|
|
Problem: Tiny version doesn't build.
Solution: Add dummy ex_var() function.
|
|
Problem: Vim9: using ":const!" is weird.
Solution: Use "var" - "final" - "const" like Dart. "let" still works for
now.
|
|
Problem: Endless loop when ":normal" feeds popup window filter.
Solution: Add the ex_normal_busy_done flag.
|
|
Problem: Vim9: assignment test fails.
Solution: Include changes to find Ex command.
|
|
Problem: Vim9: ":*" is not recognized as a range.
Solution: Move recognizing "*" into skip_range(). (closes #6838)
|
|
Problem: Expand('<stack>') does not include the final line number.
Solution: Add the line nuber. (closes #6927)
|
|
Problem: Vim9: :put ={expr} does not work inside :def function.
Solution: Add ISN_PUT. (closes #6397)
|
|
Problem: Vim9: Ex command default range is not set.
Solution: When range is not given use default. (closes #6779)
|
|
Problem: Vim9: cannot assign to local option.
Solution: Skip over "&l:" and "&g:". (closes #6749)
|
|
Problem: Vim9: cannot use " #" in a mapping.
Solution: Do not remove a comment with the EX_NOTRLCOM flag. (closes #6746)
|
|
Problem: Build failures.
Solution: Move typedef out of #ifdef. Adjust argument types. Discover
America.
|
|
Problem: Vim9: crash when compiling heredoc lines start with comment.
Solution: Skip over NULL pointers. Do not remove comment and empty lines
when fetching function lines. (closes #6743)
|
|
Problem: ":argdel" does not work like ":.argdel" as documented. (Alexey
Demin)
Solution: Make ":argdel" work like ":.argdel". (closes #6727)
Also fix giving the error "0 more files to edit".
|
|
Problem: Error messages are spread out.
Solution: Move more messages into errors.h.
|
|
Problem: Error messages are spread out and names can be confusing.
Solution: Start moving error messages to a separate file and use clear
names.
|
|
Problem: Function implementing :substitute has unexpected name.
Solution: Rename from do_sub() to ex_substitute().
|
|
Problem: Previous tab page not usable from an Ex command.
Solution: Add the "#" argument for :tabnext et al. (Yegappan Lakshmanan,
closes #6677)
|
|
Problem: Vim9: using :import in filetype plugin gives an error.
Solution: Allow commands with the EX_LOCK_OK flag. (closes #6636)
|
|
Problem: Vim9: cannot assign to / register in Vim9 script.
Solution: Adjust check for assignment in Vim9 script. (closes #6567)
|
|
Problem: Build failure without the eval feature.
Solution: Add #ifdef.
|
|
Problem: Cannot easily get the script ID.
Solution: Support expand('<SID>').
|
|
Problem: Small build fails.
Solution: Add #ifdef.
|
|
Problem: Vim9: accidentally using "x" gives a confusing error.
Solution: Disallow using ":t" in Vim9 script. (issue #6399)
|
|
Problem: Vim9: method on double quoted string doesn't work.
Solution: Recognize double quoted string. (closes #6562)
|
|
Problem: Vim9 script: cannot assign to environment variable.
Solution: Recognize environment variable assignment. (closes #6548)
Also options and registers.
|
|
Problem: Build failure with tiny version.
Solution: Add #ifdef.
|
|
Problem: Vim9: accidentally using "x" causes Vim to exit.
Solution: Disallow using ":x" or "xit" in Vim9 script. (closes #6399)
|
|
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: Vim9: error when using vim9script in TextYankPost.
Solution: Use EX_LOCKOK instead of the EX_CMDWIN flag for command that can
be used when text is locked. (closes #6529)
|
|
Problem: Vim9: cannot use mark in range.
Solution: Use the flag that a colon was seen. (closes #6528)
|
|
Problem: Vim9: No error when using a type to a window variable
Solution: Recognize the syntax and give an error. (closes #6521)
|
|
Problem: The "trailing characters" error can be hard to understand.
Solution: Add the trailing characters to the message.
|
|
Problem: Ex command error cannot contain an argument.
Solution: Add ex_errmsg() and translate earlier. Use e_trailing_arg where
possible.
|
|
Problem: Vim9: list unpack doesn't work at the script level.
Solution: Detect unpack assignment better. (closes #6494)
|
|
Problem: Build error without the eval feature.
Solution: Declare starts_with_colon. Make function local.
|
|
Problem: Vim9: allowing both quoted and # comments is confusing.
Solution: Only support # comments in Vim9 script.
|
|
Problem: Vim9: cannot use 'text'->func().
Solution: Recognize string at start of command.
|
|
Problem: Vim9: checking for Vim9 syntax is spread out.
Solution: Use in_vim9script().
|
|
Problem: Build failure in small version.
Solution: Add #ifdef.
|
|
Problem: Vim9: filter function recognized as command modifier, leading to a
crash.
Solution: Clear cmdmod after freeing items. Do not recognize a command
modifier followed by non-white space. (closes #6434)
|
|
Problem: Vim9: dict.name is not recognized as an expression.
Solution: Recognize ".name". (closes #6418)
|
|
Problem: Vim9: modifiers not cleared after compiling function.
Solution: Clear command modifiers. (closes #6396)
|
|
Problem: Vim9: parsing command checks for list twice.
Solution: Adjust how a command is parsed.
|
|
Problem: Vim9: no line continuation allowed in method call.
Solution: Handle line continuation in expression before method call.
|
|
Problem: Vim9: no line break allowed in a while loop.
Solution: Update stored loop lines when finding line breaks.
|
|
Problem: Crash when using :tabonly in an autocommand. (Yegappan Lakshmanan)
Solution: Do not allow the autocommand window to be closed.
|
|
Problem: Vim9: leaking memory when using continuation line.
Solution: Keep a pointer to the continuation line in evalarg_T. Centralize
checking for a next command.
|
|
Problem: Vim9: cannot put an operator on the next line.
Solution: Require a colon before a range to see if that causes problems.
|
