| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Using just "$" does not cause an error message.
Solution: Check for empty environment variable name. (Christian Brabandt)
|
|
Problem: Compiler warning on 64 bit windows.
Solution: Add type cast. (Mike Williams)
|
|
Problem: Comparing pointers instead of the string they point to.
Solution: Use strcmp(). (Ken Takata)
|
|
Problem: CTRL-U in Insert mode does not work after using a cursor key.
(Pine Wu)
Solution: Use the original insert start position. (Christian Brabandt)
|
|
Problem: Using exists() on a funcref for a script-local function does not
work.
Solution: Translate <SNR> to the special byte sequence. Add a test.
|
|
Problem: The '[ mark is in the wrong position after "gq". (Ingo Karkat)
Solution: Add the setmark argument to do_join(). (Christian Brabandt)
|
|
Problem: Test 62 fails.
Solution: Set the language to C. (Christian Brabandt)
|
|
Problem: Can't call a global function with "g:" in an expression.
Solution: Skip the "g:" when looking up the function.
|
|
Problem: Can't define a function starting with "g:". Can't assign a
funcref to a buffer-local variable.
Solution: Skip "g:" at the start of a function name. Don't check for colons
when assigning to a variable.
|
|
Problem: GCC 4.8 compiler warning for hiding a declaration (Francois Gannaz)
Solution: Remove the second declaration.
|
|
Problem: Duplicate code in regexec().
Solution: Add line_lbr flag to regexec_nl().
|
|
Problem: When updating the window involves a regexp pattern, an interactive
substitute to replace a "\n" with a line break fails. (Ingo
Karkat)
Solution: Set reg_line_lbr in vim_regsub() and vim_regsub_multi().
|
|
Problem: It is possible to define a function with a colon in the name. It
is possible to define a function with a lower case character if a
"#" appears after the name.
Solution: Disallow using a colon other than with "s:". Ignore "#" after the
name.
|
|
Problem: Warning for misplaced "const".
Solution: Move the "const". (Yukihiro Nakadaira)
|
|
Problem: Configure fails if $CC contains options.
Solution: Remove quotes around $CC. (Paul Barker)
|
|
Problem: Compiler warning, possibly for mismatch in parameter name.
Solution: Rename the parameter in the declaration.
|
|
Problem: Using systemlist() may cause a crash and does not handle NUL
characters properly.
Solution: Increase the reference count, allocate memory by length. (Yasuhiro
Matsumoto)
|
|
Problem: Configure check for smack doesn't work with all shells. (David
Larson)
Solution: Remove spaces in set command.
|
|
Problem: Smack support detection is incomplete.
Solution: Check for attr/xattr.h and specific macro.
|
|
Problem: Crash when using cpp syntax file with pattern using external
match. (Havard Garnes)
Solution: Discard match when end column is before start column.
|
|
Problem: Critical error in GTK, removing timer twice.
Solution: Clear the timer after removing it. (James McCoy)
|
|
Problem: Crash when BufAdd autocommand wipes out the buffer.
Solution: Check for buffer to still be valid. Postpone freeing the buffer
structure. (Hirohito Higashi)
|
|
Problem: Some test files missing from distribution.
Solution: Add pattern for newly added tests.
|
|
Problem: Using setreg() with a list of numbers does not work.
Solution: Use a separate buffer for numbers. (ZyX)
|
|
Problem: Cannot distinguish between NL and NUL in output of system().
Solution: Add systemlist(). (ZyX)
|
|
Problem: When passing input to system() there is no way to keep NUL and
NL characters separate.
Solution: Optionally use a list for the system() input. (ZyX)
|
|
Problem: Configure message for detecting smack are out of sequence.
Solution: Put the messages in the right place. (Kazunobu Kuriyama)
|
|
Problem: Crash for "vim -u NONE -N -c '&&'".
Solution: Check for the pattern to be NULL. (Dominique Pelle)
|
|
Problem: The smack feature causes stray error messages.
Solution: Remove the error messages.
|
|
Problem: Cannot use setreg() to add text that includes a NUL.
Solution: Make setreg() accept a list.
|
|
Problem: getreg() does not distinguish between a NL used for a line break
and a NL used for a NUL character.
Solution: Add another argument to return a list. (ZyX)
|
|
Problem: The string returned by submatch() does not distinguish between a
NL from a line break and a NL that stands for a NUL character.
Solution: Add a second argument to return a list. (ZyX)
|
|
Problem: ":tjump" shows "\n" as "\\n".
Solution: Skip over "\" that escapes a backslash. (Gary Johnson)
|
|
Problem: ":e +" does not position cursor at end of the file.
Solution: Check for "+" being the last character (ZyX)
|
|
Problem: Vim does not support the smack library.
Solution: Add smack support (Jose Bollo)
|
|
Problem: When some patches was not included has("patch-7.4.123") may return
true falsely.
Solution: Check for the specific patch number.
|
|
Problem: It's not that easy to check the Vim patch version.
Solution: Make has("patch-7.4.123") work. (partly by Marc Weber)
|
|
Problem: It is not easy to get the full path of a command.
Solution: Add the exepath() function.
|
|
Problem: Can't get the command that was used to start Vim.
Solution: Add v:progpath. (Viktor Kojouharov)
|
|
Problem: Escaping special characters for using "%" with a shell command is
inconsistant, parenthesis are escaped but spaces are not.
Solution: Only escape "!". (Gary Johnson)
|
|
Problem: ":%s/\n//" uses a lot of memory. (Aidan Marlin)
Solution: Turn this into a join command. (Christian Brabandt)
|
|
Problem: An error in ":options" is not caught by the tests.
Solution: Add a test for ":options". Set $VIMRUNTIME for the tests so that
it uses the current runtime files instead of the installed ones.
|
|
Problem: Error when using ":options".
Solution: Fix the entry for 'lispwords'. (Kenichi Ito)
|
|
Problem: Using ":let" for listing variables and the second one is a curly
braces expression may fail.
Solution: Check for an "=" in a better way. (ZyX)
|
|
Problem: Compiler warnings when building with Python 3.2.
Solution: Make type cast depend on Python version. (Ken Takata)
|
|
Problem: Can't build with Ruby 1.8.
Solution: Do include a check for the Ruby version. (Ken Takata)
|
|
Problem: Cursurline highlighting not redrawn when scrolling. (John
Marriott)
Solution: Check for required redraw in two places.
|
|
|
|
Problem: Dynamic Ruby doesn't work on Solaris.
Solution: Always use the stubs. (Danek Duvall, Yukihiro Nakadaira)
|
|
Problem: /usr/bin/grep on Solaris does not support -F.
Solution: Add configure check to find a good grep. (Danek Duvall)
|
