Re: Vim updates
Tony - Bram Moolenaar wrote: Ali Akcaagac wrote: On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? I don't make executables for every patched version. It simply takes too much time to do this for every patch. I'm currently checking in every patch in CVS, that already is a huge slowdown. Previously Tony made patched versions available. He stopped doing that when his computer broke down. Perhaps someone else can volunteer to do this now. Steve Hall has picked up the tools fallen from my hands ;-), and does it better than I ever did, see my earlier post on this thread. Right, I actually already have this linked on the download page, but it's not very noticable. I'll make this clearer. - Bram -- hundred-and-one symptoms of being an internet addict: 130. You can't get out of your desk even if it's time to eat or time to go to the bathroom. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Vim updates
On Sat, 2006-08-12 at 09:48 -0400, Steve Hall wrote: It uses my own configuration of the Nullsoft Installer (NSIS) instead of relying on Vim's NSIS-install.exe combo, but it otherwise contains gvim.exe, vim.exe, gvimext.dll, plus all the standard and runtime files current as of build date. Version output is given in the Notes link at each file. Hmmm, I just downloaded that file and I am not really convinced by it. It's not the same as the releases Bram does. The Menu entries in the Windows Start Menu are not identical, The colorful green icons are missing, even the name convention used gVim 7.x for example is not there. Looking deeper into c:\programs\vim I see the directory populated with plenty other directories while my previous Vim installation has just 2 or 3 iirc. Even the dir name is not Vim it's in lower case letters. I get a dialog all the time starting Vim saying I have to register vim. I therefore decided to go back to plain 7.0 release version of gVim for Windows. mfg, Ali Akcaagac
Re: Vim updates
On Sun 13-Aug-06 7:41pm -0600, Steve Hall wrote: A normal full install should have all or nearly all these (at least my install here on Fedora Core 5 does): vim70/autoload/ colors/ compiler/ doc/ ftplugin/ icons/ indent/ keymap/ lang/ macros/ plugin/ print/ spell/ syntax/ tools/ tutor/ This is fairly close to what installs on a Win system. We don't have icon/ but do have nsis/ and src/. Also the print/ directory isn't standard with a Win installation - it tagged along when I updated my runtime files with runtime/dos on the FTP site. I see bitmaps/ is not included there also. Gvim, at startup, checks for 20 separate .bmp files for each directory in 'rtp'. Not a startup speed enhancement. Is there a way to shut this bitmaps searching off? -- Best regards, Bill
Re: Vim updates
Bill McCarthy wrote: On Sun 13-Aug-06 7:41pm -0600, Steve Hall wrote: A normal full install should have all or nearly all these (at least my install here on Fedora Core 5 does): vim70/autoload/ colors/ compiler/ doc/ ftplugin/ icons/ indent/ keymap/ lang/ macros/ plugin/ print/ spell/ syntax/ tools/ tutor/ This is fairly close to what installs on a Win system. We don't have icon/ but do have nsis/ and src/. Also the print/ directory isn't standard with a Win installation - it tagged along when I updated my runtime files with runtime/dos on the FTP site. I see bitmaps/ is not included there also. Gvim, at startup, checks for 20 separate .bmp files for each directory in 'rtp'. Not a startup speed enhancement. Is there a way to shut this bitmaps searching off? src/ shouldn't be part of your production installation. You need it to compile Vim, but that should be done elsewhere than where Vim will reside for day-to-day editing. For instance, a typical production installation of Vim will reside in C:\Program Files\vim\vim70 and its subdirectories. To compile Vim, I keep the source safely apart (so if the compile fails, my production Vim doesn't get clobbered), for instance in C:\Documents and Settings\Tony\compile\vim\vim70 and its subdirectories. The letter has, among others, a runtime subdirectory for the runtime files, and a src subdirectory for the source, both of which have further subdirectories. The former should have neither src/ nor runtime/ in it. On my Linux system, $VIM/vim70/print contains only *.ps files. These should, I suppose, not be required on a normal Windows installation since on Windows the :hardcopy command doesn't use PostScript. Searching for *.bmp files is normal; it's explained as item 3 under :help toolbar-icons. If your 'rtp' directories don't have bitmap/ subdirectories, or if the latter are empty, the search should proceed rather quickly, and then you should get the built-in icons. Creating an empty bitmaps/ subdirectory in $VIMRUNTIME may or may not make the GUI startup marginally faster or slower. But this also brings us to another point: if you have bitmaps/ subdirectories with nonstandard icons in some of the 'rtp' directories, these nonstandard icons will replace the default ones on yout toolbar. There are two ways to altogether avoid searching for these icons: a) :set toolbar=text displays text-only toolbar buttons, with no icons; b) :set guioptions-=T suppresses the toolbar completely. These can be placed in your gvimrc if you have one, or (bracketed by 'if has(gui_running)') in your vimrc. Best regards, Tony.
Re: Vim updates
Ali Akcaagac wrote: Hello Bram, On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? mfg, Ali Akcaagac For Windows, Steve Hall has an automated process which generates a full upgraded installer; he uploads the latter (currently at 7.0.051, I just checked) at https://sourceforge.net/project/showfiles.php?group_id=43866package_id=39721 Best regards, Tony.
Re: Vim updates
Ali Akcaagac wrote: On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? I don't make executables for every patched version. It simply takes too much time to do this for every patch. I'm currently checking in every patch in CVS, that already is a huge slowdown. Previously Tony made patched versions available. He stopped doing that when his computer broke down. Perhaps someone else can volunteer to do this now. -- hundred-and-one symptoms of being an internet addict: 124. You begin conversations with, Who is your internet service provider? /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Vim updates
Bram Moolenaar wrote: Ali Akcaagac wrote: On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? I don't make executables for every patched version. It simply takes too much time to do this for every patch. I'm currently checking in every patch in CVS, that already is a huge slowdown. Previously Tony made patched versions available. He stopped doing that when his computer broke down. Perhaps someone else can volunteer to do this now. Steve Hall has picked up the tools fallen from my hands ;-), and does it better than I ever did, see my earlier post on this thread. Best regards, Tony.
Re: Vim updates
On Sun, 2006-08-13 at 00:04 +0200, Bram Moolenaar wrote: Previously Tony made patched versions available. He stopped doing that when his computer broke down. Perhaps someone else can volunteer to do this now. Hello Bram, I got a few replies to this request already and what Steve has to offer looks quite interesting to me. I only need to figure out (pretty soon) in how differently his setup stuff works from the one you offered. He mentioned NSIS-Install vs. Nullsoft Installer. What matters for me at the end is that I get the same files, same installation to use VIM at the end. mfg, Ali Akcaagac
Vim updates
Hello Bram, On my home Linux system I can easily compile and install every patch you release for Vim, same applies for the MorphOS versions that I from time to time create and release for our users but for Windows - which I need to use at work - I am stuck with the *.exe setup files as found on vim.org and thus can not test updates to report back problems or give feedback. Now the patchlevel has reached .051. Is there by any chance a way to release full binary setup snapshots of vim ? Say is there a way or automate process that might generate a setup say once a week and put it up on vim.org ? mfg, Ali Akcaagac
