| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Various Normal mode commands not fully tested.
Solution: Add more tests. (Yegappan Lakshmanan, closes #5751)
|
|
Problem: More functions can be used as methods.
Solution: Make various functions usable as a method.
|
|
Problem: More functions can be used as methods.
Solution: Make various functions usable as a method.
|
|
Problem: "[p" in Visual mode puts in wrong line.
Solution: Call nv_put() instead of duplicating the functionality.
(closes #4408)
|
|
Problem: Too many #ifdefs.
Solution: Graduate FEAT_MBYTE, the final chapter.
|
|
Problem: Failing test goes unnoticed because testdir/messages is not
written.
Solution: Set 'nomodifiable' only local to the buffer.
|
|
Problem: Duplicate error message for put command.
Solution: Check return value of u_save(). (Jason Franklin)
|
|
Problem: Repeating put from expression register fails.
Solution: Re-evaluate the expression register. (Andy Massimino,
closes #2945)
|
|
Problem: Unnamed register only contains the last deleted text when
appending deleted text to a register. (Wolfgang Jeltsch)
Solution: Only set y_previous when not using y_append. (Christian Brabandt)
|
|
Problem: When several lines are visually selected and one of them is short,
using put may cause a crash. (Axel Bender)
Solution: Check for a short line. (Christian Brabandt)
|
|
Problem: When a block is visually selected and put is used on the end of
the selection only one line is changed.
Solution: Check for the end properly. (Christian Brabandt, neovim issue
5781)
|
|
Problem: When a multi-byte character ends in a zero byte, putting blockwise
text puts it before the character instead of after it.
Solution: Use int instead of char for the character under the cursor.
(Luchr, closes #1403) Add a test.
|
