Re: Stable Vim version 7.1 has been released
Francois Pinard wrote: [Bram Moolenar] Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. In fact, so far that I know (and everything I know is debatable! :-), the in sequence is not part of the semantic of Makefiles, and should never be relied upon. Of course, if you experiment with various make implementations, you may observe that dependencies are usually build in sequence, but this should be seen as an accident, and not as a proof. So how do I tell make that I want to build three targets in sequence then? For generice make, not GNU make. -- Birthdays are healthy. The more you have them, the longer you live. /// 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: Stable Vim version 7.1 has been released
[Bram Moolenar] So how do I tell make that I want to build three targets in sequence then? For generice make, not GNU make. It was once forbidden to depend on GNU make in GNU packages. I guess the first package to blatantly break this rule has been GNU libc. So, most of our habits were developed for generic make. When one wants to build three targets in sequence, there is some reason for needing to build one before another, such needs are dependencies indeed, to be expressed explicitly as such. So, instead of: goal: a b c ACTIONS one writes, after having identified the real needs: goal: c ACTIONS c: b b: a Another approach I saw at times, but not so commendable, is: goal: $(MAKE) a $(MAKE) b $(MAKE) c ACTIONS -- François Pinard http://pinard.progiciels-bpi.ca
Re: Stable Vim version 7.1 has been released
Yongwei Wu wrote: On 13/05/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 I guess you already know about them. Just in case: * The home page still says Vim 7.0.243 is the current version That should be fixed automatically when the first patch goes out, which will be soon... I see it now :-) * Sources and Patches pages are not updated. Please give me the URL of where something wrong appears. That saves me a lot of time (which I don't have much of...). OK. Checking more thoroughly now. http://www.vim.org/download.php The left side still has (wow, should be a long time ago, and I did not notice it all the time): Vim 6.4 has been released. Many people have helped http://www.vim.org/sources.php The information is about Vim 7.0 and 6.4, but no 7.1. http://www.vim.org/patches.php Only 7.0 README. http://www.vim.org/subversion.php 7.1 is marked unstable there. Thanks, I've updated them. - Bram -- hundred-and-one symptoms of being an internet addict: 133. You communicate with people on other continents more than you do with your own neighbors. /// 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: Stable Vim version 7.1 has been released
Edward L. Fox wrote: On 5/14/07, David Neèas (Yeti) [EMAIL PROTECTED] wrote: On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yes, it's a bug. I can fix the problem, but not yet. Because I shall also need to delete the corresponding files in the CVS repository to keep the two repositories' consistency. If Bram would grant me such permission to delete these unnecessary files in the CVS and SVN repository, I'll do it right away. I already have the CVS writing privilege, so the only thing I need is just a permission. :-) This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. The problem is that when running configure the file is overwritten by a non-empty one. When you update from CVS later it fails. But that is OK, just ignore the error. It would be nicer if we have some way to avoid the error message, but I don't know how. -- hundred-and-one symptoms of being an internet addict: 125. You begin to wonder how often it REALLY is necessary to get up and shower or bathe. /// 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: Stable Vim version 7.1 has been released
On Mon, May 14, 2007 at 02:24:09PM +0200, Bram Moolenaar wrote: This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. I would rather say this means an additional problem in the Makefiles. If a rule requires src/auto/config.h, it should create it (directly or indirectly by dependences) when it does not exist. That's what make is for. If `make distclean' can remove src/auto/config.h and create it empty, why it cannot be created [empty] by the thing that actually needs it? This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the source tree to the same state. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
(dropping [EMAIL PROTECTED] from cc) On Mon, May 14, 2007 at 07:36:30PM +0200, Bram Moolenaar wrote: This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the source tree to the same state. Well, figure out why it breaks The above report is incorrect, it just breaks always, I'm sorry. I probably run configure so automatically that I accidentally made it work. It breaks because make starts making `scratch', `config' and `myself' simultaneously. And that appears to be due to the first targets to make vim are: scratch config myself As these targets overwrite the same files with different content, it breaks one way or another. Explicite configure bootstraps the build system and thus makes -jN safe for normal compilation. and fix it... Unfortunately my view of how a build system should work is incompatible. I can tell when something breaks and hopefully I can figure out how it happens, but I have no idea what fixed means here. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
David Necas wrote: (dropping [EMAIL PROTECTED] from cc) On Mon, May 14, 2007 at 07:36:30PM +0200, Bram Moolenaar wrote: This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the source tree to the same state. Well, figure out why it breaks The above report is incorrect, it just breaks always, I'm sorry. I probably run configure so automatically that I accidentally made it work. It breaks because make starts making `scratch', `config' and `myself' simultaneously. And that appears to be due to the first targets to make vim are: scratch config myself As these targets overwrite the same files with different content, it breaks one way or another. Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. The Vim makefile was written for a common version of all make programs. So that it builds nearly everywhere. I'm not sure supporting -jN is possible without breaking it for some system. Or including false dependencies. I don't think a parallel build helps much anyway, Vim builds rather fast (compared to say, OpenOffice, which takes half a day). Explicite configure bootstraps the build system and thus makes -jN safe for normal compilation. and fix it... Unfortunately my view of how a build system should work is incompatible. I can tell when something breaks and hopefully I can figure out how it happens, but I have no idea what fixed means here. I know, in my view make should do everything. Somehow people have accepted that some part of the building should be done separately, with the excuse that it's called configuration. Big mistake in my opinion. In quite a few programs you need to know the magic arguments to configure to be able to build. Ending up writing a shell script for it. Now why didn't they put that in the Makefile? Oh well... -- Don't drink and drive. You might hit a bump and spill your beer. /// 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: Stable Vim version 7.1 has been released
On Mon, May 14, 2007 at 11:05:24PM +0200, Bram Moolenaar wrote: Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. This means `one', `two' and `three' have to be built for `target'. More precisely any commands necessary to build any of `target's prerequisites will be fully executed before any commands necessary to build the target. The order is chosen with regard to the full dependency tree: all: a b c a: c @echo a b: @echo b c: b @echo c Single-job make has no reason to reorder the prerequisites once they are fully resolved, but AFAIK it is free to. GNU make even has a special construct to specify the order of build without implying dependency. BSD make OTOH has a `be backward compatible' option to enforce building in dependency order (it is on by default in single-job invocations). Both will give you b c a from Makefile all: a b c a: @sleep 3 @echo a b: @sleep 1 @echo b c: @sleep 2 @echo c when run with enough jobs. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. If there ever was such semantics. I've yet to see a make specification that precisely defines the build order of independent targets. The Vim makefile was written for a common version of all make programs. So that it builds nearly everywhere. I'm not sure supporting -jN is possible without breaking it for some system. Or including false dependencies. Maybe, although non-working -jN often indicates missing real dependencies. Anyway, if one neither knows he cannot use -jN nor that he can run make without running configure first -- which I suppose characterizes most people -- it works. And with independent dependencies that rewrite the same file with different content it probably cannot be fixed. I know, in my view make should do everything. Somehow people have accepted that some part of the building should be done separately, with the excuse that it's called configuration. Big mistake in my opinion. There's nothing wrong on acknowledging there are inherent chicken-egg problems and breaking the cycle explicitly. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
[Bram Moolenar] Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. In fact, so far that I know (and everything I know is debatable! :-), the in sequence is not part of the semantic of Makefiles, and should never be relied upon. Of course, if you experiment with various make implementations, you may observe that dependencies are usually build in sequence, but this should be seen as an accident, and not as a proof. Adding -jN does not change the semantics of Makefiles, but it may uncover bugs in Makefiles. I (and many other maintainers as well) used to export MAKEFLAGS=-jN (with N being a small number) just to make sure that my (our) Makefiles were not abusing of make semantics. I don't think a parallel build helps much anyway, Vim builds rather fast (compared to say, OpenOffice, which takes half a day). Using -jN does not usually spare much build time, and this was not the reason why we used it. The introduction of A[CM]_MAINTAINER_MODE (in Autoconf then Automake), to which I much objected, was symptomatic that many maintainers definitely lost hope (or at least wanted to stop aiming) for perfect Makefiles. Moreover, make is lacking in some areas and might not be worth salvaging at any price (the mere existence of aap tells me that Bram agrees at least a bit!). As a overall consequence, my starve for impeccable Makefiles faded, and I do not routinely use -jN anymore. I know, in my view make should do everything. Somehow people have accepted that some part of the building should be done separately, with the excuse that it's called configuration. Big mistake in my opinion. I've seen packages configuring on the fly while making. While nice, this also shows a few drawbacks. Nothing is perfectly black or white. Prior configuration should be seen as an optimisation issue. Configuration takes non-negligible time, and we often risk make-ing many times, so it is worth caching configurations results somehow. Also, separate configuration gives a check point where wrong configuration decisions may be corrected and retried as necessary. It is a sad thing, at least for me, that over time, configuration became so heavy, articulated over many intermediate files, and fine-grained into so many macros. It much hurts my starve for simplicity. On the other hand, the multiplication of configuration tools and independent paradigms would not be a virtue either, because of our limited ability to learn, for those of us working on many packages at once (even if admittedly, this is a disappearing trend). -- François Pinard http://pinard.progiciels-bpi.ca
Re: Stable Vim version 7.1 has been released
Bram Moolenaar wrote: Announcing: Vim (Vi IMproved) version 7.1 Excellent - thanks. Is someone going to post to a security list like full disclosure that Vim 7.1 is available, and it overcomes a serious security problem? The issue has received a brief mention in relation to patches for Vim 7.0, but now that a full release is available, perhaps an announcement should be made. John
Re: Stable Vim version 7.1 has been released
Hi Bram, On 13/05/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 I guess you already know about them. Just in case: * The home page still says Vim 7.0.243 is the current version * Sources and Patches pages are not updated. Best regards, Yongwei -- Wu Yongwei URL: http://wyw.dcweb.cn/
Re: Stable Vim version 7.1 has been released
Edward L. Fox wrote: On 5/14/07, David Neèas (Yeti) [EMAIL PROTECTED] wrote: On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yes, it's a bug. I can fix the problem, but not yet. Because I shall also need to delete the corresponding files in the CVS repository to keep the two repositories' consistency. If Bram would grant me such permission to delete these unnecessary files in the CVS and SVN repository, I'll do it right away. I already have the CVS writing privilege, so the only thing I need is just a permission. :-) This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. The problem is that when running configure the file is overwritten by a non-empty one. When you update from CVS later it fails. But that is OK, just ignore the error. It would be nicer if we have some way to avoid the error message, but I don't know how. -- hundred-and-one symptoms of being an internet addict: 125. You begin to wonder how often it REALLY is necessary to get up and shower or bathe. /// 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: Stable Vim version 7.1 has been released
On Mon, May 14, 2007 at 02:24:09PM +0200, Bram Moolenaar wrote: This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. I would rather say this means an additional problem in the Makefiles. If a rule requires src/auto/config.h, it should create it (directly or indirectly by dependences) when it does not exist. That's what make is for. If `make distclean' can remove src/auto/config.h and create it empty, why it cannot be created [empty] by the thing that actually needs it? This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the source tree to the same state. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
Yongwei Wu wrote: On 13/05/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 I guess you already know about them. Just in case: * The home page still says Vim 7.0.243 is the current version That should be fixed automatically when the first patch goes out, which will be soon... * Sources and Patches pages are not updated. Please give me the URL of where something wrong appears. That saves me a lot of time (which I don't have much of...). -- The difference between theory and practice, is that in theory, there is no difference between theory and practice. /// 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: Stable Vim version 7.1 has been released
Davic Necas wrote: On Mon, May 14, 2007 at 02:24:09PM +0200, Bram Moolenaar wrote: This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. I would rather say this means an additional problem in the Makefiles. If a rule requires src/auto/config.h, it should create it (directly or indirectly by dependences) when it does not exist. That's what make is for. This is a chicken-egg problem: You can't generate src/auto/config.h without figuring out dependencies first. I ran into this problem once and having to create an empty config.h file manually is bad. If `make distclean' can remove src/auto/config.h and create it empty, why it cannot be created [empty] by the thing that actually needs it? Hmm, perhaps that would work. Perhaps someone can try it out. The trick is to make it so that you don't rebuild too often. This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the source tree to the same state. Well, figure out why it breaks and fix it... -- hundred-and-one symptoms of being an internet addict: 126. You brag to all of your friends about your date Saturday night...but you don't tell them it was only in a chat room. /// 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: Stable Vim version 7.1 has been released
cvs vs svn Is the source moving to svn? It seems the svn portion lags a bit (timewise)behind the cvs version. Robert
Re: Stable Vim version 7.1 has been released
On 14/05/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Yongwei Wu wrote: On 13/05/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 I guess you already know about them. Just in case: * The home page still says Vim 7.0.243 is the current version That should be fixed automatically when the first patch goes out, which will be soon... I see it now :-) * Sources and Patches pages are not updated. Please give me the URL of where something wrong appears. That saves me a lot of time (which I don't have much of...). OK. Checking more thoroughly now. http://www.vim.org/download.php The left side still has (wow, should be a long time ago, and I did not notice it all the time): Vim 6.4 has been released. Many people have helped http://www.vim.org/sources.php The information is about Vim 7.0 and 6.4, but no 7.1. http://www.vim.org/patches.php Only 7.0 README. http://www.vim.org/subversion.php 7.1 is marked unstable there. -- Wu Yongwei URL: http://wyw.dcweb.cn/
Re: Stable Vim version 7.1 has been released
I finally committed the two missing files from the sf.net's shell server. Let's blame the Great Fire Wall built by the P.R.C. government. On 5/13/07, Edward L. Fox [EMAIL PROTECTED] wrote: Hi Vimmers, On 5/13/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with :help version-7.1. I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: vim -u NONE. Try different machines if possible. See :help bugs in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go 0,1,2,3,4,5,6,7,8,9,A,B,C,D /// 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/// I tried three times but still was not able to commit the latest source into the subversion repository because of the internal error of sourceforge.net. Please wait patiently. I'll try to commit again when sourceforge.net's services recovered. [EMAIL PROTECTED] svn]$ svn ci SendingContents SendingMakefile SendingREADME.txt SendingREADME_ami.txt SendingREADME_amibin.txt
Re: Stable Vim version 7.1 has been released
Edward L. Fox wrote: I finally committed the two missing files from the sf.net's shell server. Let's blame the Great Fire Wall built by the P.R.C. government. Thanks for taking care of the SVN repository! I verified that checking out vim7 gives the same result as the CVS server and the tar archives. -- hundred-and-one symptoms of being an internet addict: 119. You are reading a book and look for the scroll bar to get to the next page. /// 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: Stable Vim version 7.1 has been released
Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... -- John O'Shea Wordbank Limited 33 Charlotte Street, London W1T 1RR Direct line: +44 (0) 20 7903 8829 Fax: +44 (0) 20 7903 http://www.wordbank.com/
Re: Stable Vim version 7.1 has been released
On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
On Sun 13-May-07 6:01am -0600, Edward L. Fox wrote: I finally committed the two missing files from the sf.net's shell server. Let's blame the Great Fire Wall built by the P.R.C. government. SVN now appears to be working nicely and appears to have the full 7.1 code. Thanks! -- Best regards, Bill
Re: Stable Vim version 7.1 has been released
On 5/14/07, David Nečas (Yeti) [EMAIL PROTECTED] wrote: On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yes, it's a bug. I can fix the problem, but not yet. Because I shall also need to delete the corresponding files in the CVS repository to keep the two repositories' consistency. If Bram would grant me such permission to delete these unnecessary files in the CVS and SVN repository, I'll do it right away. I already have the CVS writing privilege, so the only thing I need is just a permission. :-) Yeti -- http://gwyddion.net/ Cheers, Edward
Re: Stable Vim version 7.1 has been released
Edward L. Fox wrote: I finally committed the two missing files from the sf.net's shell server. Let's blame the Great Fire Wall built by the P.R.C. government. Thanks for taking care of the SVN repository! I verified that checking out vim7 gives the same result as the CVS server and the tar archives. -- hundred-and-one symptoms of being an internet addict: 119. You are reading a book and look for the scroll bar to get to the next page. /// 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: Stable Vim version 7.1 has been released
Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... -- John O'Shea Wordbank Limited 33 Charlotte Street, London W1T 1RR Direct line: +44 (0) 20 7903 8829 Fax: +44 (0) 20 7903 http://www.wordbank.com/
Re: Stable Vim version 7.1 has been released
Bram Moolenaar wrote: Edward L. Fox wrote: I finally committed the two missing files from the sf.net's shell server. Let's blame the Great Fire Wall built by the P.R.C. government. Thanks for taking care of the SVN repository! I verified that checking out vim7 gives the same result as the CVS server and the tar archives. Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists That's as of 20:17 GMT, give or take -- John O'Shea Wordbank Limited 33 Charlotte Street, London W1T 1RR Direct line: +44 (0) 20 7903 8829 Fax: +44 (0) 20 7903 http://www.wordbank.com/
Re: Stable Vim version 7.1 has been released
On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yeti -- http://gwyddion.net/
Re: Stable Vim version 7.1 has been released
On 5/14/07, David Nečas (Yeti) [EMAIL PROTECTED] wrote: On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates snipped] svn: Failed to add file 'src/auto/config.h': object of the same name already exists Gah. Scrub that. Manually removing the file in question and updating again has sorted it (that's the first time I've had Subversion complain over several updates). Sorry for the noise... Actually, this is a repository bug. src/auto/config.h is fully generated therefore it should not be versioned. Yes, it's a bug. I can fix the problem, but not yet. Because I shall also need to delete the corresponding files in the CVS repository to keep the two repositories' consistency. If Bram would grant me such permission to delete these unnecessary files in the CVS and SVN repository, I'll do it right away. I already have the CVS writing privilege, so the only thing I need is just a permission. :-) Yeti -- http://gwyddion.net/ Cheers, Edward
Stable Vim version 7.1 has been released
Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with :help version-7.1. I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: vim -u NONE. Try different machines if possible. See :help bugs in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go 0,1,2,3,4,5,6,7,8,9,A,B,C,D /// 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: Stable Vim version 7.1 has been released
Hi Vimmers, On 5/13/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with :help version-7.1. I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: vim -u NONE. Try different machines if possible. See :help bugs in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go 0,1,2,3,4,5,6,7,8,9,A,B,C,D /// 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/// I tried three times but still was not able to commit the latest source into the subversion repository because of the internal error of sourceforge.net. Please wait patiently. I'll try to commit again when sourceforge.net's services recovered. [EMAIL PROTECTED] svn]$ svn ci SendingContents SendingMakefile SendingREADME.txt SendingREADME_ami.txt SendingREADME_amibin.txt SendingREADME_amisrc.txt SendingREADME_bindos.txt SendingREADME_dos.txt SendingREADME_extra.txt SendingREADME_lang.txt SendingREADME_mac.txt SendingREADME_ole.txt SendingREADME_os2.txt Sending
Stable Vim version 7.1 has been released
Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with :help version-7.1. I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: vim -u NONE. Try different machines if possible. See :help bugs in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go 0,1,2,3,4,5,6,7,8,9,A,B,C,D /// 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: Stable Vim version 7.1 has been released
Hi Vimmers, On 5/13/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1 This is a stable release of Vim, version 7.1. Since version 7.0 lots of problems were fixed and runtime files were updated. It has been one year and five days since 7.0! Most of Vim 7.1 was already available as patches for quite a while. A couple of test versions were made to spot problems in the distribution. Therefore Vim 7.1 can be considered very stable. If you are using an older version, it is highly recommended you install Vim 7.1. Several crashing bugs and a security issue were fixed. Once you have installed Vim 7.1 you can find details about the changes since Vim 7.0 with :help version-7.1. I will not make an Amiga or OS/2 binary for Vim 7.1. A Mac version is hopefully available soon on http://macvim.org/ Where to get it --- All files can be found below this directory: ftp://ftp.vim.org/pub/vim/ Information about which files to download for what system: http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1 is also available from CVS and Subversion: http://www.vim.org/cvs.php http://www.vim.org/subversion.php An overview of the files: UNIX: unix/vim-7.1.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1-extra.tar.gz extra files extra/vim-7.1-lang.tar.gz multi-language files doc/vim71html.zip help files converted to HTML MS-WINDOWS: pc/gvim71.exe self-installing, includes all runtime files pc/vim71rt.zip runtime files for binaries below pc/vim71lang.zip files for translated messages and menus pc/gvim71.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71ole.zip GUI binary with OLE support pc/gvim71_s.zipGUI binary for Windows 3.1 pc/vim71d16.zip16 bit console version for MS-DOS pc/vim71d32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71w32.zipconsole version for Windows NT/2000/XP pc/vim71src.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1.diff.gzsources + runtime files extra/vim-7.0-7.1-extra.diff.gz extra files extra/vim-7.0-7.1-lang.diff.gz multi-language files unstable/unix/vim-7.1b-7.1.diff.gz sources + runtime files unstable/extra/vim-7.1b-7.1-extra.diff.gz extra files unstable/extra/vim-7.1b-7.1-lang.diff.gzmulti-language files Mailing lists - For user questions you can turn to the Vim mailing list. There are a lot of tips, scripts and solutions. You can ask your Vim questions, but only if you subscribe. See http://www.vim.org/maillist.php#vim If you want to help Vim development or get the latest patches, subscribe to the vim-dev mailing list. See http://www.vim.org/maillist.php#vim-dev Subject specific lists: Multi-byte issues: http://www.vim.org/maillist.php#vim-multibyte Macintosh issues: http://www.vim.org/maillist.php#vim-mac Before you ask a question you should search the archives, someone may already have given the answer. Reporting bugs -- Send them to [EMAIL PROTECTED]. Please describe the problem precisely. All the time spent on answering mail is subtracted from the time that is spent on improving Vim! Always give a reproducible example and try to find out which settings or other things influence the appearance of the bug. Try starting without your own vimrc file: vim -u NONE. Try different machines if possible. See :help bugs in Vim. Send me a patch if you can! If something needs discussing with other developers, send a message to the vim-dev mailing list. You need to subscribe first. Happy Vimming! -- hundred-and-one symptoms of being an internet addict: 114. You are counting items, you go 0,1,2,3,4,5,6,7,8,9,A,B,C,D /// 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/// I tried three times but still was not able to commit the latest source into the subversion repository because of the internal error of sourceforge.net. Please wait patiently. I'll try to commit again when sourceforge.net's services recovered. [EMAIL PROTECTED] svn]$ svn ci SendingContents SendingMakefile SendingREADME.txt SendingREADME_ami.txt SendingREADME_amibin.txt SendingREADME_amisrc.txt SendingREADME_bindos.txt SendingREADME_dos.txt SendingREADME_extra.txt SendingREADME_lang.txt SendingREADME_mac.txt SendingREADME_ole.txt SendingREADME_os2.txt Sending
