On Tue, Dec 22, 2015 at 3:57 PM, Bram Moolenaar <[email protected]> wrote: > Ben Fritz wrote: >> On Monday, December 21, 2015 at 2:44:27 PM UTC-6, Bram Moolenaar wrote: > Yes, that is why we need to either use something available on every > Windows system (I don't know what though) or include wget.exe. I have > one that is about 250 Kbyte. Only problem is that I don't know where it > came from, need to check if we can distribute it. > > Including this is a good idea anyway, so you can just edit any file on > an ftp or web server "out of the box".
curl is a better choice than wget because: - it has a less restrictive license than wget - development is very active - it has many more features than wget curl should have been included with the win32 Vim 10 years ago, it would have enabled many more plugins to have network capabilities without being broken on Windows. >> > Some things that might cause problems: >> > - If the line endings are changed from LF to CR-LF then the checksum >> > will always differ. Perhaps we need two entries for each file, with >> > and without CR-LF? >> >> Don't change line endings. Just distribute Unix-style and it will work >> on Windows, too. Frankly I'm annoyed it doesn't "just work" on Unix >> with either style like it does on Windows. > > Traditionally we have always distributed runtime files with CR-LF > endings on Windows. This is indeed inconsistent, especially when > updating with git. > > I can give it a try to use LF on Windows and see what doesn't work. > There might be a few small problems, but it also solves problems. Using LF on Windows cannot possibly cause any issues, otherwise Vundle, pathogen, vim-plug, neobundle, all would be broken on Windows: they all pull the same plugin sources from GitHub. >> > - I'm not sure how to put the files in place on MS-Windows if the >> > current user can't write in the $VIMRUNTIME directory. Create a .bat >> > file perhaps? >> >> I've never really had success with getting admin rights in a .bat >> file. Supposedly there is the "runas" command but I don't think >> provides what we want. >> >> Really you'd either need to roll an .exe file/installer or tell the >> user to run an elevated command prompt. Telling an average user that >> will make their eyes glaze over. Although to be fair Vim users >> probably aren't "average" users in many ways. > > We may need to include a small exe that runs the commands. Just like > the installer runs with extra priveleges. However, there is an answer > on stackoverflow that might work: These are contortions to avoid the actual solution, which is to provide up-to-date win32 binaries at vim.org. >> All in all, though, I think such a plugin would not be very useful for >> most people. > > Best is to have something check for updates, click on "update now", and > it all works perfectly... Dreaming? In the meantime, providing up-to-date win32 installers is a reasonable and automate-able middle ground. --- Justin M. Keyes -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
