| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
Problem: ":bufdo" may start at a deleted buffer.
Solution: Find the first not deleted buffer. (Shane Harper)
https://github.com/vim/vim/commit/v7-4-646
|
| |
|
|
|
|
|
| |
Problem: Range for :bdelete does not work. (Ronald Schild)
Solution: Also allow unloaded buffers.
https://code.google.com/p/vim/source/detail?name=v7-4-585
|
| |
|
|
|
|
|
|
| |
Problem: Giving an error for ":0wincmd w" is a problem for some
plugins.
Solution: Allow the zero in the range. (Marcin Szamotulski)
https://code.google.com/p/vim/source/detail?r=v7-4-568
|
| |
|
|
|
|
|
| |
Problem: :argdo, :bufdo, :windo and :tabdo don't take a range.
Solution: Support the range. (Marcin Szamotulski)
https://code.google.com/p/vim/source/detail?r=v7-4-566
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
Patch 7.4.561
Problem: Ex range handling is wrong for buffer-local user commands.
Solution: Check for CMD_USER_BUF. (Marcin Szamotulski)
https://code.google.com/p/vim/source/detail?name=v7-4-561
|
|
|
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
https://code.google.com/p/vim/source/detail?name=v7-4-542
|
