Re: Vim version 7.1a BETA has been released
On 2007-05-06, Bram Moolenaar [EMAIL PROTECTED] wrote: Gary Johnson wrote: I noticed that filetype.vim does not include the patch that I submitted to this list 2006-07-25 to fix the recognition of mutt temporary files on SunOS. Is there something else I can do to have this patch accepted? It was still in the todo list. There are many items I still didn't have time for, unfortunately. I assume you have properly tested this change. I'll include this one now. Thank you. I was concerned that it hadn't made it onto the list. I didn't realize you had such a backlog of changes. I've been using it in my $VIMRUNTIME/filetype.vim since July without any problems or errors that I know of. Best regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: Vim version 7.1a BETA has been released
On 2007-05-06, Gary Johnson [EMAIL PROTECTED] wrote: On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote: Compiles as a breeze :-). Yes indeed. I've compiled it so far on SunOS 5.8 and HP-UX 10.20. I may try Cygwin if I'm feeling adventurous enough. I've never done that except from Cygwin sources. Well, that was really easy. I built just the console version for Cygwin and it seems to work fine in PuTTY over an ssh connection. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: Vim version 7.1a BETA has been released
On Sun, 06 May 2007 14:46:22 +0200, A.J.Mechelynck [EMAIL PROTECTED] wrote: Michael Henry wrote: Gary Johnson wrote: On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote: (Warning: In the ln command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. I used to find this hard to remember until I realized that 'ln' and 'cp' are very similar. The 'cp' command copies one or more sources to a destination; the 'ln' command links one or more sources to a destination as well. I tend to think of 'ln -s' as copy using symlinks. The order and meaning of the arguments is the same between the commands, which I now find consistent and intuitive. The problem is, cp -v file1 file2 outputs `file1' - `file2' (the data has been copied from file1 to file2) but ln -sv file1 file2 outputs file2 - file1 (file2 is now a link pointing to file1). I still have to call up the help or the manual every time I invoke it. Just remember that for all of cp, ln and mv, the existing file comes first. I think the confusion arises because people think of ln as create a link, so they see ln x y as create a link x..., which it isn't. It makes more sense if you think of it this way: mv x ymove file x to file y cp x ycopy file x to file y ln x ylink file x to file y -- Matthew Winn
Re: Vim version 7.1a BETA has been released
Matthew Winn wrote: On Sun, 06 May 2007 14:46:22 +0200, A.J.Mechelynck [EMAIL PROTECTED] wrote: Michael Henry wrote: I used to find this hard to remember until I realized that 'ln' and 'cp' are very similar. The problem is, cp -v file1 file2 outputs `file1' - `file2' (the data has been copied from file1 to file2) but ln -sv file1 file2 outputs file2 - file1 It makes more sense if you think of it this way: mv x ymove file x to file y cp x ycopy file x to file y ln x ylink file x to file y Agreed, this is what makes the parameter order intuitive and consistent to me. But I can see confusion creeping in when the '-v' flag of the 'ln' command reverses the order of the filenames, as shown in Tony's example above. Fortunately, I almost never use '-v' so it can't confuse me :-) Michael Henry
Re: Vim version 7.1a BETA has been released
Gary Johnson wrote: On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote: Bram Moolenaar wrote: Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. Once you have installed Vim 7.1a BETA you can find details about the changes since Vim 7.0 with :help version-7.1. [...] Compiles as a breeze :-). Yes indeed. I've compiled it so far on SunOS 5.8 and HP-UX 10.20. I may try Cygwin if I'm feeling adventurous enough. I've never done that except from Cygwin sources. The binary is now in /usr/local/vim (but we still have /usr/local/vim70 as a backup); the runtime files go in /usr/local/vim/vim71a and below, where the binary will find them with no problem (and the 7.0 runtime files in /usr/local/vim/vim70 [or wherever] aren't touched). I think some directories were omitted from the paths in that paragraph and that it should read: The binary is now in /usr/local/bin/vim (but we still have /usr/local/bin/vim70 as a backup); the runtime files go in /usr/local/share/vim/vim71a and below, where the binary will find them with no problem (and the 7.0 runtime files in /usr/local/share/vim/vim70 [or wherever] aren't touched). er, yes. I should have reread it once more. (Warning: In the ln command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. Regards, Gary Yes. When linking to the same name in a different directory, I find it easier to omit the link name altogether, as shown for matchit.txt Best regards, Tony. -- He was a modest, good-humored boy. It was Oxford that made him insufferable.
Re: Vim version 7.1a BETA has been released
On 2007-05-05, Bram Moolenaar [EMAIL PROTECTED] wrote: Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. I noticed that filetype.vim does not include the patch that I submitted to this list 2006-07-25 to fix the recognition of mutt temporary files on SunOS. Is there something else I can do to have this patch accepted? Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: Vim version 7.1a BETA has been released
Gary Johnson wrote: I noticed that filetype.vim does not include the patch that I submitted to this list 2006-07-25 to fix the recognition of mutt temporary files on SunOS. Is there something else I can do to have this patch accepted? It was still in the todo list. There are many items I still didn't have time for, unfortunately. I assume you have properly tested this change. I'll include this one now. -- Q: Should I clean my house or work on Vim? A: Whatever contains more bugs. /// 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 version 7.1a BETA has been released
Gary Johnson wrote: On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote: (Warning: In the ln command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. I used to find this hard to remember until I realized that 'ln' and 'cp' are very similar. The 'cp' command copies one or more sources to a destination; the 'ln' command links one or more sources to a destination as well. I tend to think of 'ln -s' as copy using symlinks. The order and meaning of the arguments is the same between the commands, which I now find consistent and intuitive. Michael Henry
Re: Vim version 7.1a BETA has been released
Michael Henry wrote: Gary Johnson wrote: On 2007-05-05, A.J.Mechelynck [EMAIL PROTECTED] wrote: (Warning: In the ln command as used here, the target name comes before the link name. I find this counter-intuitive.) It's not just me then. I have to think carefully about that every time I use ln. I used to find this hard to remember until I realized that 'ln' and 'cp' are very similar. The 'cp' command copies one or more sources to a destination; the 'ln' command links one or more sources to a destination as well. I tend to think of 'ln -s' as copy using symlinks. The order and meaning of the arguments is the same between the commands, which I now find consistent and intuitive. Michael Henry The problem is, cp -v file1 file2 outputs `file1' - `file2' (the data has been copied from file1 to file2) but ln -sv file1 file2 outputs file2 - file1 (file2 is now a link pointing to file1). I still have to call up the help or the manual every time I invoke it. Best regards, Tony. -- Celebrate Hannibal Day this year. Take an elephant to lunch.
Vim version 7.1a BETA has been released
Announcing: Vim (Vi IMproved) version 7.1a BETA This is a BETA release of Vim 7.1. It consists of Vim 7.0 plus all patches and updated runtime files. I expect this to be stable, since the patches have been used by many people already. This BETA is mainly to check that the files has been setup properly. It's been almost a year since the last one! Please report every problem you find! It will only be a few days until the 7.1 release, so please take a little time right now to check it out. Once you have installed Vim 7.1a BETA you can find details about the changes since Vim 7.0 with :help version-7.1. Testing --- This is a BETA test version. Please give it a good test and report anything that isn't right. That includes a crash but also a typo in the documentation. I will not make an Amiga or OS/2 binary for Vim 7.1a. 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/unstable/ Information about which files to download for what system (don't use the links, they are still for Vim 7.0): http://www.vim.org/download.php A list of mirror sites can be found here: http://www.vim.org/mirrors.php Vim 7.1a is also available from CVS (when it works again) and with Aap: http://www.vim.org/develop.php An overview of the files: UNIX: unix/vim-7.1a.tar.bz2 sources + runtime files, bzip2 compressed VARIOUS: extra/vim-7.1a-extra.tar.gz extra files extra/vim-7.1a-lang.tar.gz multi-language files doc/vim71ahtml.zip help files converted to HTML MS-WINDOWS: pc/gvim71a.exe self-installing, includes all runtime files pc/vim71art.zip runtime files pc/vim71alang.zip files for translated messages and menus pc/gvim71a.zip GUI binary for Windows 95/98/NT/2000/XP pc/gvim71aole.zip GUI binary with OLE support pc/gvim71a_s.zipGUI binary for Windows 3.1 (untested) pc/vim71ad16.zip16 bit console version for MS-DOS pc/vim71ad32.zipconsole version for MS-DOS/Windows 95/98 pc/vim71aw32.zipconsole version for Windows NT/2000/XP pc/vim71asrc.zipsources for PC (with CR-LF) DIFFS TO PREVIOUS RELEASE: unix/vim-7.0-7.1a.diff.gz sources + runtime files extra/vim-7.0-7.1a-extra.diff.gz extra files extra/vim-7.0-7.1a-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: 53. To find out what time it is, you send yourself an e-mail and check the Date: field. /// 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///
