Christian Brabandt wrote:
> This is a test case:
> ./vim -u NONE -U NONE -N -c "set enc=latin1|echo '.*d' =~ '\<.*d'"
>
>
> Unfortunately, I haven't been able to create a test case for this. For
> some reason, when running the test suite, it doesn't trigger the crash
> (probably, because reg_
This is a test case:
./vim -u NONE -U NONE -N -c "set enc=latin1|echo '.*d' =~ '\<.*d'"
Unfortunately, I haven't been able to create a test case for this. For
some reason, when running the test suite, it doesn't trigger the crash
(probably, because reg_buf is set somewhere)
Attached is a bette
Christian Brabandt 256bit.org> writes:
>
> Hi txp!
>
> On Do, 24 Jan 2013, txp wrote:
>
> > Hello everybody,
> > I am new to vim (today is my second day) and I ran into a problem which was
identified as a bug by the extremely
> helpful people on the #vim irc channel.
> > This is the situation
Hi txp!
On Do, 24 Jan 2013, txp wrote:
> Hello everybody,
> I am new to vim (today is my second day) and I ran into a problem which was
> identified as a bug by the extremely helpful people on the #vim irc channel.
> This is the situation: when I run vim with the pathogen plugin, which is
> int
Hello everybody,
I am new to vim (today is my second day) and I ran into a problem which was
identified as a bug by the extremely helpful people on the #vim irc channel.
This is the situation: when I run vim with the pathogen plugin, which is
integrated into the vimrc with "call pathogen#infect()