aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/testdir/test_put.vim
Commit message (Collapse)AuthorAge
* vim-patch:8.1.0811: too many #ifdefsDaniel Hahler2019-08-22
| | | | | | Problem: Too many #ifdefs. Solution: Graduate FEAT_MBYTE, the final chapter. https://github.com/vim/vim/commit/30276f2beb248557c6b33cd5418bca8b7084b0a5
* vim-patch:8.1.1373: "[p" in Visual mode puts in wrong lineJan Edmund Lazo2019-05-23
| | | | | | | Problem: "[p" in Visual mode puts in wrong line. Solution: Call nv_put() instead of duplicating the functionality. (closes vim/vim#4408) https://github.com/vim/vim/commit/0ab190c05706b1c72e6e2ca4d990febfa81cf886
* vim-patch:8.1.0119: failing test goes unnoticed because messages is not writtenJan Edmund Lazo2019-04-01
| | | | | | | Problem: Failing test goes unnoticed because testdir/messages is not written. Solution: Set 'nomodifiable' only local to the buffer. https://github.com/vim/vim/commit/ec12d6490923fb5ff147ebf7e28d32f2b4977e3b
* vim-patch:8.1.0118: duplicate error message for put commandJan Edmund Lazo2019-04-01
| | | | | | Problem: Duplicate error message for put command. Solution: Check return value of u_save(). (Jason Franklin) https://github.com/vim/vim/commit/f52f9ea8f5fb3df51a308c56f2bf66f735ef3ca7
* vim-patch:8.0.0681: unnamed register only contains the last deleted textJan Edmund Lazo2019-04-01
| | | | | | | 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) https://github.com/vim/vim/commit/18d90b95c49d9ff1c635dd762864022aab8e71f1
* vim-patch:8.1.0022: repeating put from expression register failsJan Edmund Lazo2018-08-29
| | | | | | | Problem: Repeating put from expression register fails. Solution: Re-evaluate the expression register. (Andy Massimino, closes vim/vim#2945) https://github.com/vim/vim/commit/833093bfb0e4a7f89b5adc66babcfa8ac09cfda9
* vim-patch:8.0.0234,8.0.0236,8.0.0225 (#8052)KunMing Xie2018-03-04
| | | | | | | | | | | | | | | | | | | | | vim-patch:8.0.0234: crash when using put in Visual mode 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) https://github.com/vim/vim/commit/941c12da3c087fd04aa6c120a76bf28f19349d96 vim-patch:8.0.0236: gcc complains about uninitialized variable Problem: Gcc complains that a variable may be used uninitialized. Confusion between variable and label name. (John Marriott) Solution: Initialize it. Rename end to end_lnum. https://github.com/vim/vim/commit/6a717f17ec6b09634be1c29e0ac4c35213f7b32d vim-patch:8.0.0225: put in Visual block mode terminates early 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) https://github.com/vim/vim/commit/9957a10d0f0c34d8083af6ed66e198e4796038e0
* vim-patch:8.0.0225: put in Visual block mode terminates early (#8040)UTkarsh Maheshwari2018-02-21
| | | | | | | 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) https://github.com/vim/vim/commit/9957a10d0f0c34d8083af6ed66e198e4796038e0
* vim-patch:8.0.0222: blockwise put on multi-byte char (#8030)KunMing Xie2018-02-20
Note: code change was covered by c2a18216114bae75b6d6a2c7f1a68db04578abce 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 vim/vim#1403) Add a test. https://github.com/vim/vim/commit/c81299684b2b9045e56525d3da3f45e8440fbf0d