On 17/02/09 16:03, Ben Fritz wrote:
>
>
> On Feb 17, 2:17 am, Tony Mechelynck<[email protected]>
> wrote:
>
>> When I was on Windows, I always directly invoked the binary, with no
>> noticeable ill effects.
>>
>
> Right, nothing wrong with that...it's just that when you upgrade Vim,
Only for a new minor release, which isn't often enough to bother me, and
requires extra work anyway with my workflow, to get the source and make
it ready for compilation.
Not for a new patchlevel.
> you'll need to go through the hassle of setting your path to the new
> Vim install directory instead of the old. I've been meaning to change
> all my file associations to the batch files as well to get around the
> upgrade issue there too, but have never gotten around to it.
Of course, on Linux (where I am now), "make install" (or "make
installvimbin" which I use for my "tiny" version named vi) takes care of
placing the binary in the $PATH; and my existing softlinks (in
/usr/local/bin/ : view -> vim, vimdiff -> vim, gvim -> vim, gview ->
vim, etc. etc. etc.) don't need any change.
Best regards,
Tony.
--
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense.
-- E. W. Dijkstra
Oh, yeah? "Against oppression, insurrection is for the people the most
imprescriptible of rights and the holiest of duties" (Declaration of the
Rights of Man and Citizen, 1789). If someone, be he named Dijkstra or
anything else, tries to tell me in what languages I "may" program and to
put his "laws" to execution, I shall treat him as an oppressor. You
Vimmers be the judges of whether the years I spent programming mostly in
COBOL (and some in assembly language) crippled my mind.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
