| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Compiler warnings for unitinialized variables. (John Little)
Solution: Initialize the variables.
|
|
Problem: ":52wincmd v" still gives an invalid range error. (Charles
Campbell)
Solution: Skip over white space.
|
|
|
|
Problem: Wrong cursor positioning when 'linebreak' is set and lines wrap.
Solution: (Christian Brabandt)
|
|
Problem: Using getcurpos() after "$" in an empty line returns a negative
number.
Solution: Don't add one when this would overflow. (Hirohito Higashi)
|
|
Problem: Matching with a virtual column has a lot of overhead on very long
lines. (Issue 310)
Solution: Bail out early if there can't be a match. (Christian Brabandt)
Also check for CTRL-C at every position.
|
|
Problem: Redrawing problem with 'relativenumber' and 'linebreak'.
Solution: Temporarily reset 'linebreak' and restore it in more places.
(Christian Brabandt)
|
|
Problem: Unicode character properties are outdated.
Solution: Update the tables with the latest version.
|
|
Problem: No error for eval('$').
Solution: Check for empty name. (Yasuhiro Matsumoto)
|
|
Problem: Mapping CTRL-C in Visual mode doesn't work. (Ingo Karkat)
Solution: Call get_real_state() instead of using State directly.
|
|
Problem: Address type of :wincmd depends on the argument.
Solution: Check the argument.
|
|
Problem: Can't build with tiny features. (Ike Devolder)
Solution: Add #ifdef.
|
|
Problem: Building with dynamic library does not work for Ruby 2.2.0
Solution: Change #ifdefs and #defines. (Ken Takata)
|
|
|
|
Problem: Having CTRL-C interrupt or not does not check the mode of the
mapping. (Ingo Karkat)
Solution: Use a bitmask with the map mode. (Christian Brabandt)
|
|
Problem: Giving an error for ":0wincmd w" is a problem for some plugins.
Solution: Allow the zero in the range. (Marcin Szamotulski)
|
|
|
|
Problem: Non-ascii vertical separater characters are always redrawn.
Solution: Compare only the one byte that's stored. (Thiago Padilha)
|
|
|
|
Problem: :argdo, :bufdo, :windo and :tabdo don't take a range.
Solution: Support the range. (Marcin Szamotulski)
|
|
Problem: Ranges for arguments, buffers, tabs, etc. are not checked to be
valid but limited to the maximum. This can cause the wrong thing
to happen.
Solution: Give an error for an invalid value. (Marcin Szamotulski)
Use windows range for ":wincmd".
|
|
Problem: FEAT_OSFILETYPE is used even though it's never defined.
Solution: Remove the code. (Christian Brabandt)
|
|
Problem: No test for replacing on a tab in Virtual replace mode.
Solution: Add a test. (Elias Diem)
|
|
Problem: Segfault with wide screen and error in 'rulerformat'. (Ingo Karkat)
Solution: Check there is enough space. (Christian Brabandt)
|
|
Problem: Ex range handling is wrong for buffer-local user commands.
Solution: Check for CMD_USER_BUF. (Marcin Szamotulski)
|
|
Problem: Memory leak using :wviminfo. Issue 296.
Solution: Free memory when needed. (idea by Christian Brabandt)
|
|
Problem: Appending a block in the middle of a tab does not work correctly
when virtualedit is set.
Solution: Decrement spaces and count, don't reset them. (James McCoy)
|
|
Problem: When the X server restarts Vim may get stuck.
Solution: Destroy the application context and create it again. (Issue 203)
|
|
Problem: One more small issue.
Solution: Update function proto.
|
|
Problem: Failed commands in Python interface not handled correctly.
Solution: Restore window and buffer on failure.
|
|
Problem: test_close_count may fail for some combination of features.
Solution: Require normal features.
|
|
Problem: Missing part of patch 7.4.519.
Solution: Copy back regprog after calling vim_regexec.
|
|
Problem: Various small issues.
Solution: Fix those issues.
|
|
|
|
Problem: Langmap applies to Insert mode expression mappings.
Solution: Check for Insert mode. (Daniel Hahler)
|
|
Problem: "ygn" may yank too much. (Fritzophrenic) Issue 295.
Solution: Check the width of the next match. (Christian Brabandt)
|
|
Problem: curs_rows() function is always called with the second argument
false.
Solution: Remove the argument. (Christian Brabandt)
validate_botline_win() can then also be removed.
|
|
|
|
Problem: Function name not recognized correctly when inside a function.
Solution: Don't check for an alpha character.
|
|
Problem: Function name not recognized correctly when inside a function.
Solution: Don't check for an alpha character.
|
|
Problem: Using "vit" does not select a multi-byte character at the end
correctly.
Solution: Advance the cursor over the multi-byte character. (Christian
Brabandt)
|
|
Problem: Repeated use of vim_snprintf() with a number.
Solution: Move these vim_snprintf() calls into a function.
|
|
Problem: Highlighting for multi-line matches is not correct.
Solution: Stop highlight at the end of the match. (Hirohito Higashi)
|
|
Problem: Warnings for unused arguments when compiling with a combination of
features.
Solution: Add "UNUSED".
|
|
Problem: Since patch 7.4.232 "1,3s/\n//" joins two lines instead of three.
(Eliseo MartÃnez) Issue 287
Solution: Correct the line count. (Christian Brabandt)
Also set the last used search pattern.
|
|
Problem: Using a range for window and buffer commands has a few problems.
Cannot specify the type of range for a user command.
Solution: Add the -addr argument for user commands. Fix problems. (Marcin
Szamotulski)
|
|
Problem: Crash when doing a range assign.
Solution: Check for NULL poiter. (Yukihiro Nakadaira)
|
|
|
|
Problem: Cannot build with tiny and small features. (Taro Muraoka)
Solution: Add #ifdef around CMD_USER.
|
|
Problem: Crash when computing buffer count. Problem with range for user
commands. Line range wrong in Visual area.
Solution: Avoid segfault in compute_buffer_local_count(). Check for
CMD_USER when checking type of range. (Marcin Szamotulski)
|
