From: "John Beckett", Tue, December 01, 2009 10:14 pm > > Sorry, I should have reported this to Steve because the issue > came up on the wiki. I put my understanding of the problem and > the best solution for a user here: > http://vim.wikia.com/wiki/Running_diff > > We are talking about Windows systems, and I think the "best > solution" is to install the GnuWin32 diff package (I believe > that all that is needed is to copy the *.exe/*.dll files into a > directory in your PATH).
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? -- Steve Hall [ digitect dancingpaper com ] -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
