| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | tests: Migrate legacy test close_count. | Lucas Hoffmann | 2016-05-20 |
| | | |||
| * | vim-patch:7.4.565 | Felipe Morales | 2015-04-28 |
| | | | | | | | | | | | | 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". https://code.google.com/p/vim/source/detail?r=v7-4-565 | ||
| * | vim-patch:7.4.530-531 | Felipe Morales | 2015-04-28 |
| Specify different kinds of counts for commands. Updated ex commands generator scripts. Includes fixes to comments from patch 7.4.531 Original message: Problem: Many commands take a count or range that is not using line numbers. Solution: For each command specify what kind of count it uses. For windows, buffers and arguments have "$" and "." have a relevant meaning. (Marcin Szamotulski) https://code.google.com/p/vim/source/detail?r=v7-4-530 https://code.google.com/p/vim/source/detail?r=v7-4-531 Add legacy tests for 7.4.530 https://code.google.com/p/vim/source/detail?r=1e6d87a36dcdca231721dde8cbbc26610fb3df27 | |||