Hi Bram!
On Mi, 13 Jan 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > > > Bram,
> > > > this patch fies an issue reported by David Fishburn about a misbehaving
> > > > searchpairpos(). I traced it back to syntax.c and I think what happens
> > > > is, that Vim gets confused
Christian Brabandt wrote:
> > > Bram,
> > > this patch fies an issue reported by David Fishburn about a misbehaving
> > > searchpairpos(). I traced it back to syntax.c and I think what happens
> > > is, that Vim gets confused about the current syntax stack. I added a
> > > newstyle test, that
Hi Bram!
On Di, 12 Jan 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > Bram,
> > this patch fies an issue reported by David Fishburn about a misbehaving
> > searchpairpos(). I traced it back to syntax.c and I think what happens
> > is, that Vim gets confused about the current
Christian Brabandt wrote:
> Bram,
> this patch fies an issue reported by David Fishburn about a misbehaving
> searchpairpos(). I traced it back to syntax.c and I think what happens
> is, that Vim gets confused about the current syntax stack. I added a
> newstyle test, that lets the problem
On Mon, Jan 11, 2016 at 3:06 PM, Christian Brabandt
wrote:
> Bram,
> this patch fies an issue reported by David Fishburn about a misbehaving
> searchpairpos(). I traced it back to syntax.c and I think what happens
> is, that Vim gets confused about the current syntax stack. I
Bram,
this patch fies an issue reported by David Fishburn about a misbehaving
searchpairpos(). I traced it back to syntax.c and I think what happens
is, that Vim gets confused about the current syntax stack. I added a
newstyle test, that lets the problem reproduce, given the plugin from
David.