Hi Cesar!
On Do, 24 Apr 2014, Cesar Romani wrote:
> I'm using vim 7.3.264 on Windows 7.
>
> '[count]find file' works fine. If I do, for example ':2find file'
> it finds the correct version of file, and if I do ':3find file' it
> outputs the message 'E347: No more file "file" found in path' what
Hi Andrew!
On Sa, 19 Apr 2014, Andrew wrote:
> Given a text file with the following two lines:
>
> first line
> second line
>
> If you now go to the second line and yank it, then go to the first line and
> type in
>
> "_ddp
>
> What I'd expect to happen is:
>
> second line
>
On Do, 24 Apr 2014, Ingo Karkat wrote:
> Hello Vim developers,
>
> my plugins' automated test suite found another regression. When
> reformatting lines with gq{motion}, the start of change mark '[ does not
> point to the start of the first line [0, lnum, 1, 0] any more, but
> instead to after th
On 24/04/2014 10:46 a.m., Ben Fritz wrote:
> On Thursday, April 24, 2014 10:23:51 AM UTC-5, Cesar wrote:
>> I'm using vim 7.3.264 on Windows 7.
>>
>> ...
>>
>> If I do for example ':14tabf file' it always finds the first version...
>>
>> It used to work with older vim versions.
>
> Did you actuall
Bram,
I noticed an unexpected break of test62 (in the catch E474 part).
This patch fixes it for me:
diff --git a/src/testdir/test62.in b/src/testdir/test62.in
--- a/src/testdir/test62.in
+++ b/src/testdir/test62.in
@@ -2,6 +2,7 @@ Tests for tab pages
STARTTEST
:so small.vim
+:lang C
:" Simple
See the following minimal example. The curly braces do not have the
same effect outside of an if block.
$ cat >test.sh <<"EOF"
#!/bin/sh
if true; then
# do and the braces have the same unusual color
while true; do
{ true; }
done # hl as red for error
for f; do
{ true; } || break
d
