Mercurial > vim

view src/testdir/test_command_count.ok @ 6472:22f95a018b13 v7.4.565

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.4.565 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".
author Bram Moolenaar <bram@vim.org>
date Wed, 07 Jan 2015 15:57:17 +0100
parents 82c6a3bddb23
children a88d4dc02bf4
line wrap: on
line source

RangeArguments 2 4
RangeArguments 1 5
RangeArgumentsAll 1 5
RangeArguments 2 2
RangeWindows 3 5
RangeWindows 1 5
RangeWindowsAll 1 5
RangeLoadedBuffers 2 4
RangeLoadedBuffers 1 4
RangeLoadedBuffersAll 1 4
RangeBuffers 2 5
RangeBuffers 1 5
RangeBuffersAll 1 5
RangeTabs 2 5
RangeTabs 1 5
RangeTabsAll 1 5
RangeLines 2 5
LocalRangeLines 2 5

5argu E16: Invalid range
4argu d
1argu a
100b E16: Invalid range
0close E16: Invalid range
$close 4
$+close E16: Invalid range
$tabe 2
$+tabe E16: Invalid range
0tabm x