Steve Hall wrote:
> I'm concerned about relying on things outside the default Vim
> distro since it is too complicated for me to package. Between
> the various versions of Windows and 32- and 64-bit
> complexities, building binaries in addition to the Vim ones is
> too risky.
>
> Same goes for putting things outside the application's
> directory. On more and more systems administrators forbid this
> anyway.
>
> The gVim Black installers should just work, I feel these
> issues on Windows should be solved by Vim, not the installer.
>
>> I'm not sure how the Cream install can best solve the
>> problem. If the Vim directory is placed in the PATH, and if
>> licensing allows, putting the current GnuWin32 files in the
>> Vim directory would be best (and remove diffexpr + MyDiff
>> from _vimrc).
>
> I guess I still don't quite understand why MyDiff is
> required, internally Vim should be able to deal with it's own
> diff.exe. User options should be allowed to override it, but
> why does the default install have to condition use of diff in
> the vimrc instead of the binary?
I'm too lazy to check at the moment (I build my own Vim), but
does the official Windows distribution of Vim include diff.exe?
I have an old system with "Vim without Cream" and its diff.exe
(given "--version" argument) says
diff - GNU diffutils version 2.7
On Windows, the diff that I use is GNU diffutils 2.8.7 but I
think it requires gutils.dll.
A quick test makes me think that the diff 2.7 in Cream will work
with no MyDiff function. I can well understand that you do not
want to fiddle around distributing the current diffutils, but
perhaps you could try removing the following from vimrc:
set diffexpr=MyDiff()
the MyDiff() function
then check if gvim can still do differences. I'm not entirely
sure why, but my quick test indicates that with gvim.exe and
diff.exe in the same directory (a directory that is not in the
PATH), gvim can still invoke diff with no MyDiff. I guess that
whatever system call gvim is using to spawn diff is causing
Windows to search the same directory as gvim.
John
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
