From: Benjamin Fritz [mailto:fritzophre...@gmail.com]
> I see mostly what I would expect, but the line that matches the
> "concealends" syntax rule is missing the listchars replacement for the
> first concealed end. See conceal_bug_start.png.
> Now, I press 'j' several times to move past all the
From: Benjamin Fritz [mailto:fritzophre...@gmail.com]
> I see mostly what I would expect, but the line that matches the
> "concealends" syntax rule is missing the listchars replacement for the
> first concealed end. See conceal_bug_start.png.
> Now, I press 'j' several times to move past all the
From: Vince Negri
> This bug crept in with changeset 2391 -
> Maybe there is a place where "syntax_seqnr" needs to be incremented but isn't?
This patch (against 2391) appears to fix the broken concealends. Not the blank
lines in a region though.
diff -r 0371401d9d33 src/syntax.c
--- a/src/syn
On Tuesday 27 July 2010 08:37:31 Vince Negri wrote:
> This bug crept in with changeset 2391 - "Give each syntax item
> a sequence number, so that we know when it starts and.." rev
> 2390 is fine, 2391 is broken.
you cannot use that first number to communicate -- the "Give
each item a sequence n
From: sc [mailto:tooth...@swbell.net]
> you cannot use that first number to communicate -- the "Give
> each item a sequence number" changeset for me was 2432 -- that
> number is different for everybody -- you must use the horking
> and unambiguous 0371401d9d33
> sorry to go off topic
No need to
Vince Negri wrote:
> > you cannot use that first number to communicate -- the "Give
> > each item a sequence number" changeset for me was 2432 -- that
> > number is different for everybody -- you must use the horking
> > and unambiguous 0371401d9d33
>
> > sorry to go off topic
>
> No need to ap
Vince Negri wrote:
Glad to hear from you again Vince. I've been making changes to the
conceal feature and had not received remarks from you yet. Especially
about the 'concealcursor' option. And also this issue with consecutive
matches of concealed items.
> > This bug crept in with changeset
Benjamin Fritz wrote:
> I brought these up initially in another thread but I'm posting a new
> one so it doesn't get lost in the shuffle. And I said I'd try to
> reproduce it from the latest update and without my .vimrc.
>
> I'm running the latest version of Vim 7.3 on Windows XP, compiled
> mys
On Jul 28, 11:17 am, Bram Moolenaar wrote:
>
> I have fixed this now. Please check for any remaining problems.
>
Confirmed, latest build fixes all the problems I saw in my test file.
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
