Tony Mechelynck wrote:
> Bill McCarthy wrote:
>> On Fri 3-Aug-07 8:00am -0600, Chris Sutcliffe wrote:
>>
>>>> Patch 7.1.048
>>>> Problem:    The matchparen plugin doesn't update the match when scrolling 
>>>> with
>>>>             the mouse wheel. (Ilya Bobir)
>>>> Solution:   Set the match highlighting for text that can be scrolled into 
>>>> the
>>>>             viewable area without moving the cursor. (Chris Lubinski)
>>>> Files:      runtime/plugin/matchparen.vim
>>> I've rsync'd against ftp.nluug.nl and it doesn't contain this change.
>>> Going forward, is the runtime directory in CVS / SVN the definitive
>>> source for the latest runtime files?
>> No, they appear to be a definitive source for patches
>> against the distribution.
>>
>> However, patches don't update all runtime files which
>> eventually make it to the runtime archives.  I regularly
>> update from ftp://ftp.home.vim.org/pub/vim/runtime/dos.
>>
>> It is a bit out of date currently.  As you pointed out,
>> matchparen.vim is an old version.  The help files updated by
>> patches are also not included in the archive yet.
>>
>> It would be wonderful if Bran had an automated way of
>> updating the runtime archives each time he updating the CVS
>> archive for runtime files.
>>
>> Better yet, it would be nice if runtime files are either all
>> updated in CVS or none of them are updated - since using the
>> runtime archive is quite easy.  This would avoid all the
>> patch errors we now get when the runtime archive is more
>> recent than CVS.
>>
> 
> I also rsync after ftp.nluug.nl (after applying the patches when there are 
> any, and once daily even if there are no patches). Since my rsync 
> command-line 
> includes --delete this cleans away any .orig or .rej files created by 
> patching 
> errors, but it also means that the runtimes from the ftp archive make it to 
> my 
> $VIMRUNTIME in preference to the result of patching. As of this writing, the 
> plugin/matchparen.vim found there has (in its third line) a date of 2006 Oct 
> 12. (As a side note, this means that my current Vim declares itself to be 
> 7.1.048 but is actually 7.1.047.)
> 
> Let's hope the new matchparen version "eventually" finds its way to the ftp 
> site.
> 
> 
> Best regards,
> Tony.

Update: It did! (along with a number of other files' upgrades). Time for

        make -C src installruntime 2>&1 |tee instrt.log


Best regards,
Tony.
-- 
"You are old," said the youth, "and your programs don't run,
        And there isn't one language you like;
Yet of useful suggestions for help you have none --
        Have you thought about taking a hike?"

"Since I never write programs," his father replied,
        "Every language looks equally bad;
Yet the people keep paying to read all my books
        And don't realize that they've been had."

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui