Hello Vim users,

Announcing:  Vim (Vi IMproved) version 7.2b BETA

This is a BETA release of Vim 7.2.  It consists of Vim 7.1 plus all
patches, updated runtime files and some more.

I expect this to be stable, since most of the patches have been used by
many people already.  However, I did include several patches the last
few days, this might break something.

Please report every problem you find!  The time until a 7.2 release
depends on how many problems are reported.

The biggest addition since 7.1 is floating point support.

Since version 7.2a several reported problems were fixed.  The MS-Windows
binary is now built with VC 2003, so that it also works on MS-Windows 98
and ME.  Should also work on Vista.

Once you have installed Vim 7.2b BETA you can find details about the
changes since Vim 7.1 with ":help version-7.2".

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.2b.  A Mac version is
hopefully available soon on http://macvim.org/  and/or from the MacVim
project at http://code.google.com/p/macvim/

Gratitude
---------

If you like Vim, this is the way to say thanks:
http://iccf-holland.org/clinic.html

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.1):
        http://www.vim.org/download.php

A list of mirror sites can be found here:
        http://www.vim.org/mirrors.php

Vim 7.2b is also available from CVS.  Subversion will follow later.
        http://www.vim.org/cvs.php
        http://www.vim.org/subversion.php

The Aap files have also been updated.

An overview of the files below "unstable":

UNIX:
unix/vim-7.2b.tar.bz2           sources + runtime files, bzip2 compressed

MS-WINDOWS one-size-fits-all:
pc/gvim72b.exe                  self-installing, includes all runtime files

VARIOUS:
extra/vim-7.2b-extra.tar.gz     source files for non-Unix platforms
extra/vim-7.2b-lang.tar.gz      multi-language files
doc/vim72bhtml.zip              help files converted to HTML

MS-WINDOWS separate files:
pc/vim72brt.zip                 runtime files
pc/vim72blang.zip               files for translated messages and menus
pc/gvim72b.zip                  GUI binary for Windows 95/98/NT/2000/XP
pc/gvim72bole.zip               GUI binary with OLE support
pc/gvim72b_s.zip                GUI binary for Windows 3.1 (untested)
pc/vim72bd32.zip                console version for MS-DOS/Windows 95/98
pc/vim72bw32.zip                console version for Windows NT/2000/XP
pc/vim72bsrc.zip                sources for PC (with CR-LF)

DIFFS TO PREVIOUS RELEASE:
unix/vim-7.2a-7.2b.diff.gz          sources + runtime files
extra/vim-7.2a-7.2b-extra.diff.gz   extra files
extra/vim-7.2a-7.2b-lang.diff.gz    multi-language files

There is no 16-bit DOS version, I could not build it.

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, discuss new features 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 <b...@vim.org>.  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:
224. You set up your own Web page. You set up a Web page for each
     of your kids... and your pets.

 /// Bram Moolenaar -- B...@Moolenaar.net -- 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    ///

Hello Vim users,

Announcing:  Vim (Vi IMproved) version 7.2b BETA

This is a BETA release of Vim 7.2.  It consists of Vim 7.1 plus all
patches, updated runtime files and some more.

I expect this to be stable, since most of the patches have been used by
many people already.  However, I did include several patches the last
few days, this might break something.

Please report every problem you find!  The time until a 7.2 release
depends on how many problems are reported.

The biggest addition since 7.1 is floating point support.

Since version 7.2a several reported problems were fixed.  The MS-Windows
binary is now built with VC 2003, so that it also works on MS-Windows 98
and ME.  Should also work on Vista.

Once you have installed Vim 7.2b BETA you can find details about the
changes since Vim 7.1 with ":help version-7.2".

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.2b.  A Mac version is
hopefully available soon on http://macvim.org/  and/or from the MacVim
project at http://code.google.com/p/macvim/

Gratitude
---------

If you like Vim, this is the way to say thanks:
http://iccf-holland.org/clinic.html

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.1):
        http://www.vim.org/download.php

A list of mirror sites can be found here:
        http://www.vim.org/mirrors.php

Vim 7.2b is also available from CVS.  Subversion will follow later.
        http://www.vim.org/cvs.php
        http://www.vim.org/subversion.php

The Aap files have also been updated.

An overview of the files below "unstable":

UNIX:
unix/vim-7.2b.tar.bz2           sources + runtime files, bzip2 compressed

MS-WINDOWS one-size-fits-all:
pc/gvim72b.exe                  self-installing, includes all runtime files

VARIOUS:
extra/vim-7.2b-extra.tar.gz     source files for non-Unix platforms
extra/vim-7.2b-lang.tar.gz      multi-language files
doc/vim72bhtml.zip              help files converted to HTML

MS-WINDOWS separate files:
pc/vim72brt.zip                 runtime files
pc/vim72blang.zip               files for translated messages and menus
pc/gvim72b.zip                  GUI binary for Windows 95/98/NT/2000/XP
pc/gvim72bole.zip               GUI binary with OLE support
pc/gvim72b_s.zip                GUI binary for Windows 3.1 (untested)
pc/vim72bd32.zip                console version for MS-DOS/Windows 95/98
pc/vim72bw32.zip                console version for Windows NT/2000/XP
pc/vim72bsrc.zip                sources for PC (with CR-LF)

DIFFS TO PREVIOUS RELEASE:
unix/vim-7.2a-7.2b.diff.gz          sources + runtime files
extra/vim-7.2a-7.2b-extra.diff.gz   extra files
extra/vim-7.2a-7.2b-lang.diff.gz    multi-language files

There is no 16-bit DOS version, I could not build it.

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, discuss new features 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 <b...@vim.org>.  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:
224. You set up your own Web page. You set up a Web page for each
     of your kids... and your pets.

 /// Bram Moolenaar -- B...@Moolenaar.net -- 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    ///

On 13/07/08 20:16, Bram Moolenaar wrote:

Works well so far: compiles flawlessly, both as Huge +gui_gtk2
+gui_gnome +perl +python +ruby +tcl and as Tiny -x11 -mouse; in both
cases -tag_old_static +xterm_save. The GUI has reloaded my session with
no problems (yet).

Happy Vimming everyone!

Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
68. Your cat always puts viruses on your dogs homepage

On Jul 13 20:16, Bram Moolenaar wrote:

Builds fine on Cygwin, all tests successful.

Thanks,
Corinna

--
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat

Vim-7.2b.2 BETA builds and works flawlessly for me so far on
Linux x86.  I only noticed 2 typos in ":help version-7.2".
See attached patch.

-- Dominique

typos-version7.txt.patch 2K Download

Hi,

I just wrote a simple function in vim script and needed 12 backslashes
to escape a space!  I haven't sat down and tried to figure out exactly
why it needs that many, but it won't work with less.

It's a useful function too, so here it is:

""""""""""""""""""""""""
func! AddDir(setting, path)
    if isdirectory(a:path)
        exec "set " . a:setting "+=" . substitute(a:path, " ", "\\\\\\\\\\\\ ",
"g")
    endif
endfunc
""""""""""""""""""""""""

Then in your .vimrc/_vimrc file you can use it like this:

""""""""""""""""""""""""
call AddDir("path", "F:/Program Files/Microsoft Platform SDK/VC/include")
""""""""""""""""""""""""

The directory path will be added to the given setting if and only if
it exists, and the path may be provided without having to escape
spaces.  For me this is handy as it allows me to use the same .vimrc
on different machines with different paths, without the 'path' setting
getting out of hand.

I also have a similar function called AddFile, where isdirectory is
replaced with filereadable.  Useful for the 'dict' setting.

12 backslashes does seem a bit excessive though :-)
Rob.

--

Robert Webb,
MineSweeper3D - Take Minesweeper to a whole new dimension!
http://www.software3d.com/Mines3D

LOL. I like it! But I don't, too. This is one of the things that does
annoy me about Vimscript. But it's shared by pretty much every language
that has the same concept of escape characters. Here's the breakdown:

1. The :set command needs a backslash before a space. One backslash.
2. The 'path' option needs a backslash before a space, because for
    compatibility a space is an alternative to a comma. Since :set needs
    this escaped too, we have three now.
3. In the substitute replacement, backslashes must be escaped, so double
    each. Six now.
4. In double quotes, you need to escape backslashes. Double them again.
    Twelve.

Step 4 can easily be avoided by using single quotes, leaving six.

exec "set " . a:setting "+=" . substitute(a:path, " ", '\\\\\\ ', "g")

And for options other than 'path', you will only need two.

Ben.