Bill McCarthy wrote:
> On Fri 3-Aug-07 3:24pm -0600, Tony Mechelynck wrote:
>
>> 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.
>
> I use a simply "copy /u" which only copies new files and
> files newer than on my machine - so I never get
> "downgraded."
>
Here "cp" cannot (as far as I'm aware) copy remote files: what I use is
rsync -avzcP --delete --exclude="/dos/" ftp.nluug.nl::Vim/runtime/ ./runtime/
2>&1 | tee rsync.log
vim -es -u NONE -c '%s/^.*\r//' -cx rsync.log
(two lines, which constitute a shell scriptlet), followed, if there is at
least one updated file other than doc/tags, by
make -C src installruntime 2>&1 |tee instrt.log
The result is that my runtime files are made a copy of those on the rsync
server (excluding runtime/dos/ and anything under it) by copying any that are
different or absent on the client and deleting any that are absent on the
server. Even if some runtime files are "not yet" up to the latest patchlevel,
at least the result is consistent, no files are kept which should be deleted,
and, by running the above at least once every 24h, I don't "lag behind" more
than by an "acceptable" amount by respect to the FTP server.
...yesterday evening, when I announced it, my plugin/matchparen.vim was indeed
upgraded to 2007 Jul 30, and 16 other runtime files were updated at the same
time.
Best regards,
Tony.
--
If you're like most homeowners, you're afraid that many repairs
around your home are too difficult to tackle. So, when your furnace
explodes, you call in a so-called professional to fix it. The
"professional" arrives in a truck with lettering on the sides and
deposits a large quantity of tools and two assistants who spend the
better part of the week in your basement whacking objects at random
with heavy wrenches, after which the "professional" returns and gives
you a bill for slightly more money than it would cost you to run a
successful campaign for the U.S. Senate.
And that's why you've decided to start doing things yourself.
You figure, "If those guys can fix my furnace, then so can I. How
difficult can it be?"
Very difficult. In fact, most home projects are impossible,
which is why you should do them yourself. There is no point in paying
other people to screw things up when you can easily screw them up
yourself for far less money. This article can help you.
-- Dave Barry, "The Taming of the Screw"
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
