On Mon, Apr 12, 2010 at 8:08 AM, Tony Mechelynck
<[email protected]> wrote:
> On 11/04/10 22:16, Bram Moolenaar wrote:
>>
>> Christian Brabandt wrote:
>>
>>> Are you considering any patches from
>>> http://groups.google.com/group/vim_dev/web/vim-patches
>>> for inclusion?
>>
>> Yes, but many of these patches are not mature.  E.g., first one,
>> "Improved regular expression engine", is still lacking the tests to
>> verify that it doesn't break anything.  That's a pity, because it can
>> make syntax highlighting much faster.
>>
>> I want to avoid that I include something that triggers a long sequence
>> of bug fixes.  "Works fine for me" is not always a good indication.
>> 7.3 is going to be a stable release, thus I don't want to take too much
>> risc.  Part of my work will be to estimate the risc, which involves
>> carefully looking through the code changes.
>>
>
> It is true that they are in different stages of development. Here are my top
> five; not in preference order.
>
> #14 (Vince Negri's conceal/ownsyntax/cursorbind) already has a long track
> record. I first heard about it when I first learned about Steve Hall's Vim
> for Windows, that must have been in Vim 6.2 or 6.3 time, and it was not new
> even then. Has documentation. Maybe too controversial (not enough
> "mainline"-like) to be included by default? OTOH it has been victim of
> bit-rotting in the past (i.e. conflict with "mainline" patches) and of
> course bringing it in would eliminate that problem forever. A compile-time
> option maybe (or two, or three)? You're the boss.

This thread has been a good reminder to renew my sponsorship, in part
because Vim deserves the support, and in part so I can vote again for
this patch!  I've never been clear why this patch should be
controversial, though.

Best wishes,

Nicholas

-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

To unsubscribe, reply using "remove me" as the subject.

Reply via email to