I'm unsubscribing from the list. Please CC me if you'd like to talk
about this fix.
On Mon, Jan 31, 2011 at 18:39, Gustavo Niemeyer wrote:
>>> Bram, have you had a moment to ponder about this issue? Is one of the
>>> approaches reasonable or is there anything else to be investigated?
>>
>> It's
>> Bram, have you had a moment to ponder about this issue? Is one of the
>> approaches reasonable or is there anything else to be investigated?
>
> It's in the todo list, I'll look into it when I get to it.
Awesome, thank you.
--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/blog
htt
Gustavo Niemeyer wrote:
> Bram, have you had a moment to ponder about this issue? Is one of the
> approaches reasonable or is there anything else to be investigated?
It's in the todo list, I'll look into it when I get to it.
--
Did you ever see a "Hit any key to continue" message in a music p
Bram, have you had a moment to ponder about this issue? Is one of the
approaches reasonable or is there anything else to be investigated?
On Thu, Jan 27, 2011 at 09:39, Gustavo Niemeyer wrote:
> Hi Bram,
>
>> That doesn't look like the right solution, since it restarts from the
>> start of the l
Hi Bram,
> That doesn't look like the right solution, since it restarts from the
> start of the line instead of using the column from the match.
It feels like the right thing to do, since even though the line was
already being processed, it's fully processed with a different goal.
> You say that
Gustavo Niemeyer wrote:
> For lack of luck, below is a patch to fix the bug.
>
> The problem is caused by the fact that the syncing processes the line
> til the end, so the second call to sync_finish_line() refuses to
> process it again (current_finished == TRUE).
>
> Sorry for the trouble.
>
> - // Must restart the line to process highlighting now.
> - syn_start_line();
Sorry, the patch is reversed.
--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/blog
http://niemeyer.net/twitter
--
You received this message from the "vim_dev" maillis
> Thanks! I'm also wishing for better luck. :-)
For lack of luck, below is a patch to fix the bug.
The problem is caused by the fact that the syncing processes the line
til the end, so the second call to sync_finish_line() refuses to
process it again (current_finished == TRUE).
Sorry for the tr
> I must admit that for someone who's just joined the list you seem pretty
> arrogant.
I'm fine with people calling me an arrogant for no reason and crying
about investing their time on me, but first they must provide some
kind of useful information Lech. ;-)
> Here's your answer:
Your answer is
On 26-Jan-2011 Gustavo Niemeyer wrote:
[...]
> > It also needed to have syntax highlighting turned on, and the syn clear was
> > needed to get a clean start at every sourcing; your example had neither the
> > syntax on nor the syn clear.
>
> Yes, I assumed I was talking to the developers of vim,
(...)
> then just the ' " ' is highlighted as String, which is expected (see :help
> syn-sync-minlines).
No, it's not expected. Let's read the help together:
"""
If the "minlines={N}" argument is given, the parsing always starts at least
that many lines backwards. This can be used if the parsin
Gustavo Niemeyer wrote:
Perhaps the following will be of interest:
Sorry, but I don't understand what you mean. You've provided exactly
the same syntax logic I did, but reordered, and your version continues
to expose the same bug.
I see no bug. I've tried it with -u NONE -N, sourced
Hi Ben,
> How are you testing this?
>
> I have a file identical to what you've provided for your syntax:
(...)
> The double quotes aren't colorized.
It is not the double quotes that should be colorized, it is the string
itself. This is a *region*. Open the file in the beginning to see the
proper
On Tue, 25 Jan 2011, Gustavo Niemeyer wrote:
(Charles Campbell wrote:)
Perhaps the following will be of interest:
syn on
syn clear
[ed. followed by your original :syn/:hi commands]
Sorry, but I don't understand what you mean. You've provided exactly
the same syntax logic I did, but reorde
> Perhaps the following will be of interest:
Sorry, but I don't understand what you mean. You've provided exactly
the same syntax logic I did, but reordered, and your version continues
to expose the same bug.
--
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/blog
http://niemeyer.net/t
Gustavo Niemeyer wrote:
Greetings,
I'm trying to sync up a very simple syntax and being unable to
do so. It feels a bit like a bug, but it's quite possible that I just
misunderstand how it works.
I've nailed down the problem to a very simple example:
syn sync match fooSync grouphere NONE /
Would anyone else know what's going on?
On Mon, Jan 24, 2011 at 10:54, Gustavo Niemeyer wrote:
> Greetings,
>
> I'm trying to sync up a very simple syntax and being unable to
> do so. It feels a bit like a bug, but it's quite possible that I just
> misunderstand how it works.
>
> I've nailed down
> Have a look at help for:
> :syn-sync
>
> You might want to add ":syn sync fromstart" to an file type plugin.
Thanks for the suggestion, but that's of course already been done way
before posting the bug report here, and fromstart is not an option.
The code looks correct, but I'm probably missing
On 24-Jan-2011 Gustavo Niemeyer wrote:
> Greetings,
>
> I'm trying to sync up a very simple syntax and being unable to
> do so. It feels a bit like a bug, but it's quite possible that I just
> misunderstand how it works.
>
> I've nailed down the problem to a very simple example:
>
>syn sync
Greetings,
I'm trying to sync up a very simple syntax and being unable to
do so. It feels a bit like a bug, but it's quite possible that I just
misunderstand how it works.
I've nailed down the problem to a very simple example:
syn sync match fooSync grouphere NONE /^foo\>/
syn region fooSt
20 matches
Mail list logo
