aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/testdir/test_put.vim
Commit message (Collapse)AuthorAge
* test: move oldtests to test directory (#22536)dundargoc2023-03-07
| | | | | The new oldtest directory is in test/old/testdir. The reason for this is that many tests have hardcoded the parent directory name to be 'testdir'.
* vim-patch:9.0.1376: accessing invalid memory with put in Visual block mode ↵zeertzjq2023-03-04
| | | | | | | | | | (#22505) Problem: Accessing invalid memory with put in Visual block mode. Solution: Adjust the cursor column if needed. https://github.com/vim/vim/commit/1c73b65229c25e3c1fd8824ba958f7cc4d604f9c Co-authored-by: Bram Moolenaar <Bram@vim.org>
* vim-patch:8.2.0369: various Normal mode commands not fully testedzeertzjq2022-07-14
| | | | | | | | | | Problem: Various Normal mode commands not fully tested. Solution: Add more tests. (Yegappan Lakshmanan, closes vim/vim#5751) https://github.com/vim/vim/commit/1671f4488105ee12a6a8558ae351436c26ab55fc Cherry-pick a fix from patch 8.2.3162. Omit test_iminsert.vim as previous patches to that file are N/A, and Nvim doesn't support iminsert=2 either, so that test isn't useful.
* vim-patch:9.0.0011: reading beyond the end of the line with put command (#19166)zeertzjq2022-06-30
| | | | | Problem: Reading beyond the end of the line with put command. Solution: Adjust the end mark position. https://github.com/vim/vim/commit/d25f003342aca9889067f2e839963dfeccf1fe05
* vim-patch:8.2.5016: access before start of text with a put command (#18742)zeertzjq2022-05-26
| | | | | Problem: Access before start of text with a put command. Solution: Check the length is more than zero. https://github.com/vim/vim/commit/2a585c85013be22f59f184d49612074fd9b115d7
* vim-patch:8.2.3661: test for put with large count failszeertzjq2022-02-18
| | | | | | Problem: Test for put with large count fails. Solution: Adjust the counts in the test. https://github.com/vim/vim/commit/8bc07e800c2af36686aadd4178cc2671f5c454d4
* vim-patch:8.2.3601: check for overflow in put count does not work wellSean Dewar2022-02-17
| | | | | | | | | | | | | | | Problem: Check for overflow in put count does not work well. Solution: Improve the overflow check. (Ozaki Kiichi, closes vim/vim#9102) https://github.com/vim/vim/commit/fa53722367c3793fda95dac665af74b8651065e9 Add some casts as Nvim uses size_t variables in some places. We could technically adjust the logic to check for overflow outside of size_t's range, but it's much easier to just port the patch exactly (also means we can use the same tests). v:sizeoflong is N/A, so convert the 64-bit tests to Lua and use the FFI to check long's size.
* vim-patch:8.2.3577: overflow check fails with 32 intsSean Dewar2022-02-17
| | | | | | Problem: Overflow check fails with 32 ints. Solution: Only test with 64 bit ints. https://github.com/vim/vim/commit/0f0044125c2a5dcde2c4605efc39d2e237eed024
* vim-patch:8.2.3573: cannot decide whether to skip test that fails with 64 bitSean Dewar2022-02-17
| | | | | | | | | | Problem: Cannot decide whether to skip test that fails with 64 bit ints. (closes vim/vim#9072) Solution: Add v:sizeofint, v:sizeoflong and v:sizeofpointer. Improve the check for multiply overflow. https://github.com/vim/vim/commit/69b3072d984480935ec412b32b97fea974d2b689 Omit v:sizeof{int,long,pointer} as they're only really used for tests.
* vim-patch:8.2.3570: Test_very_large_count fails on 32bit systemsSean Dewar2022-02-17
| | | | | | Problem: Test_very_large_count fails on 32bit systems. Solution: Bail out when using 32 bit numbers. (closes vim/vim#9072) https://github.com/vim/vim/commit/ec6e63079dde24a1d74b4103775e74d00f9215ec
* vim-patch:8.2.3493: large count test fails on MS-WindowsSean Dewar2022-02-17
| | | | | | Problem: Large count test fails on MS-Windows. Solution: Skip the test on MS-Windows. https://github.com/vim/vim/commit/cddd5ac911707034ca27f10037c4b1b523188c47
* vim-patch:8.2.3492: crash when pasting too many timesSean Dewar2022-02-17
| | | | | | | | | | | | | | | | | | | Problem: Crash when pasting too many times. Solution: Limit the size to what fits in an int. (closes vim/vim#8962) https://github.com/vim/vim/commit/eeed1c7ae090c17f4df51cf97b2a9e4d8b4f4dc7 Note that this overflow check pretty bad. It also doesn't work well on Windows (where sizeof(int) == sizeof(long)). This is all temporary; everything here is rewritten in future patches anyway. e_resulting_text_too_long was already cherry-picked. totlen is size_t in Nvim, but is int in Vim. This means we'll need some casts. We could technically adjust the logic in do_put to use the entire range of size_t in stuff like totlen, but there's not much gain, and it's much easier to just port the patch like Vim as was done before (also allows us to use the same tests).
* vim-patch:8.2.3581: reading character past end of linezeertzjq2022-01-29
| | | | | | Problem: Reading character past end of line. Solution: Correct the cursor column. https://github.com/vim/vim/commit/0b5b06cb4777d1401fdf83e7d48d287662236e7e
* vim-patch:8.2.3540: the mark '] is wrong after put with a countzeertzjq2022-01-29
| | | | | | Problem: The mark '] is wrong after put with a count. (Naohiro Ono) Solution: Use the right line number. (closes vim/vim#8956) https://github.com/vim/vim/commit/f47ebf1e1a0a6473b10fb4c92c9c6427aab4dc91
* vim-patch:8.2.3497: put test fails when run by itselfzeertzjq2022-01-29
| | | | | | Problem: Put test fails when run by itself. Solution: Source check.vim. (Dominique Pellé, closes vim/vim#8990) https://github.com/vim/vim/commit/a9173d06f7ca320fc84f4ffa993861d21710bc41
* vim-patch:8.2.3455: using a count with "gp" leaves '] in wrong positionzeertzjq2022-01-29
| | | | | | Problem: Using a count with "gp" leaves '] in wrong position. (Naohiro Ono) Solution: Correct the mark position. (closes vim/vim#8899) https://github.com/vim/vim/commit/56858e4ed4e338e15821767b8303b06099e40384
* vim-patch:8.2.3454: using a count with "gp" leave cursor in wrong positionzeertzjq2022-01-29
| | | | | | | Problem: Using a count with "gp" leave cursor in wrong position. (Naohiro Ono) Solution: Count the inserted lines. (closes vim/vim#8899) https://github.com/vim/vim/commit/23003e51e18371afda4420d9e171a3dcba5a31cc
* chore: fix typos (#16506)dundargoc2021-12-28
| | | | | | | | | Co-authored-by: Gregory Anders <8965202+gpanders@users.noreply.github.com> Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com> Co-authored-by: Christoph Hasse <hassec@users.noreply.github.com> Co-authored-by: Alef Pereira <ealefpereira@gmail.com> Co-authored-by: AusCyber <willp@outlook.com.au> Co-authored-by: kylo252 <59826753+kylo252@users.noreply.github.com>
* feat(eval/method): partially port v8.1.1996Sean Dewar2021-11-26
| | | | | | | | | | | | | | | | Problem: More functions can be used as methods. Solution: Make various functions usable as a method. https://github.com/vim/vim/commit/aad222c9c9a1e4fe6ae5a1fe95bb084619be0e65 Partial port as this does not include eval.txt change for listener_add. Cherry-pick eval.txt changes for: - bufadd from v8.1.1626: https://github.com/vim/vim/commit/5ca1ac373ae62b37152cb6f85916b402eda520a5 - setloclist and setqflist headers from: https://github.com/vim/vim/commit/b0d45e7f5354375edd02afafde3bd37dac1515ff Correct eval.txt typo for settabwinvar method call (matches latest Vim).
* vim-patch:8.2.3677: after a put the '] mark is on the last byte (#16442)Christian Clason2021-11-26
| | | | | | Problem: After a put the '] mark is on the last byte of a multi-byte character. Solution: Move it to the first byte. (closes vim/vim#9047) https://github.com/vim/vim/commit/4d07253a485819b3a9fd923d263e722ea2109c12
* vim-patch:8.2.1547: various comment problemsJan Edmund Lazo2020-10-18
| | | | | | Problem: Various comment problems. Solution: Update comments. https://github.com/vim/vim/commit/02c037a4be6aeb7f6376e7dcc3ab41cfc6db3ede
* 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
generated by cgit (git 2.34.1) at 2026-01-11 11:53:17 +0000