Vim 8.1 is released!

171 views
Skip to first unread message

Bram Moolenaar

unread,
May 17, 2018, 2:18:50 PM5/17/18
to vim-an...@vim.org, vim...@vim.org, v...@vim.org, vim...@vim.org

Hello Vim users!

Announcing: Vim (Vi IMproved) version 8.1


This is a minor release with many small improvements and lots of bug
fixes. The main new feature is the terminal window. I have put up a
few screenshots on the Vim website:
https://www.vim.org/vim-8.1-released.php

Once you have installed Vim 8.1 you can find details about the changes
since Vim 8.1 with:
:help version8.1
Or view it online:
https://raw.githubusercontent.com/vim/vim/master/runtime/doc/version8.txt


Gratitude
---------

If you like Vim, please consider helping poor children in the south of
Uganda: http://iccf-holland.org


Where to get it
---------------

The best way to obtain the latest Vim is using Git. Summary:
git clone https://github.com/vim/vim.git
More information here: https://www.vim.org/git.php

For MS-Windows most of you will want the self-installing executable:
https://ftp.nluug.nl/pub/vim/pc/gvim81.exe

Information about which files to download for what system:
https://www.vim.org/download.php

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


The files available for download:

UNIX:
sources + runtime files, bzip2 compressed:
https://ftp.nluug.nl/pub/vim/unix/vim-8.1.tar.bz2

VARIOUS:
help files converted to HTML:
https://ftp.nluug.nl/pub/vim/doc/vim81html.zip

MS-WINDOWS one-size-fits-all:
Self-installing, includes all runtime files, loads libraries dynamically:
https://ftp.nluug.nl/pub/vim/pc/gvim81.exe

MS-WINDOWS separate files:
Runtime files:
https://ftp.nluug.nl/pub/vim/pc/vim81rt.zip
GUI binary for Windows 95/98/NT/2000/XP/7:
https://ftp.nluug.nl/pub/vim/pc/gvim81.zip
GUI binary with OLE support:
https://ftp.nluug.nl/pub/vim/pc/gvim81ole.zip
Console version for Windows NT/2000/XP/7:
https://ftp.nluug.nl/pub/vim/pc/vim81w32.zip
Sources for PC (with CR-LF):
https://ftp.nluug.nl/pub/vim/pc/vim81src.zip

For debugging:
https://ftp.nluug.nl/pub/vim/pc/gvim81.pdb
https://ftp.nluug.nl/pub/vim/pc/gvim81ole.pdb
https://ftp.nluug.nl/pub/vim/pc/vim81w32.pdb

AMIGA:
Only runtime and sources are provided, no binary:
https://ftp.nluug.nl/pub/vim/amiga/vim81rt.tgz
https://ftp.nluug.nl/pub/vim/amiga/vim81src.tgz


Omitted in this version are:
- The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.
- The 32-bit console version for MS-DOS/Windows 95/98
- The 16 bit MS-Windows version


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 https://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
https://www.vim.org/maillist.php#vim-dev

Subject specific lists:
Macintosh issues: https://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 <vim...@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.

Alternatively, create an issue at github and/or a pull request.
Please try to write a test that reproduces the problem and will pass
once it is fixed. See https://github.com/vim/vim


Happy Vimming!


--
INSPECTOR END OF FILM: Move along. There's nothing to see! Keep moving!
[Suddenly he notices the cameras.]
INSPECTOR END OF FILM: (to Camera) All right, put that away sonny.
[He walks over to it and puts his hand over the lens.]
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

Bram Moolenaar

unread,
May 17, 2018, 3:22:56 PM5/17/18
to vim...@googlegroups.com, L. A. Walsh, vim-an...@vim.org, vim...@vim.org, v...@vim.org, vim...@vim.org

> Bram Moolenaar wrote:
> > Hello Vim users!
> >
> > Announcing: Vim (Vi IMproved) version 8.1
> >
> >
> > This is a minor release with many small improvements and lots of bug
> > fixes. The main new feature is the terminal window. I have put up a
> > few screenshots on the Vim website:
> > https://www.vim.org/vim-8.1-released.php
> >
> ----
> It's not clear if this that binary is a 64-bit version ...
> 32-bit runs between 10-15% slower on 64-bit machines.

It is 32 bit. Previous comparisons show that the 32 bit version is a
bit faster. Where do you get the information that it would be slower?

There was a 64 bit version somehwere, but it isn't very popular.

--
JOHN CLEESE PLAYED: SECOND SOLDIER WITH A KEEN INTEREST IN BIRDS, LARGE MAN
WITH DEAD BODY, BLACK KNIGHT, MR NEWT (A VILLAGE
BLACKSMITH INTERESTED IN BURNING WITCHES), A QUITE
EXTRAORDINARILY RUDE FRENCHMAN, TIM THE WIZARD, SIR
LAUNCELOT

Ken Takata

unread,
May 17, 2018, 3:37:03 PM5/17/18
to vim_dev
Hi Bram,

2018/5/18 Fri 3:18:50 UTC+9 Bram Moolenaar wrote:
> Hello Vim users!
>
> Announcing: Vim (Vi IMproved) version 8.1

Congratulations!

However, Netrw doesn't work on 8.1.
It seems that the patch 8.0.0002 was accidentally reverted and needs to be
applied again.
(I think this mistake would have been easily found if you have released a beta
version.)


And I also found two small mistake in version8.txt:

--- a/runtime/doc/version8.txt
+++ b/runtime/doc/version8.txt
@@ -22104,7 +22104,7 @@ Files: src/Makefile, src/option.c,
Patch 8.0.1238
Problem: Incremental search only shows one match.
Solution: When 'incsearch' and 'hlsearch' are both set highlight all
- matches. (haya14busa, itchyny closes #2198)
+ matches. (haya14busa, itchyny, closes #2198)
Files: runtime/doc/options.txt, src/ex_getln.c, src/proto/search.pro,
src/search.c, src/testdir/test_search.vim

@@ -22595,7 +22595,7 @@ Solution: Remove bogus typedef.
Files: src/os_macosx.m

Patch 8.0.1316 (after 8.0.1312)
-Problem: Build still fails on Mac. (chdiza)
+Problem: Build still still fails on Mac. (chdiza)
Solution: Remove another bogus typedef.
Files: src/os_mac_conv.c

The first one was my mistake, a comma was missing.
The second one was changed by Dominique's patch, however the double "still"
was intentional, I think.

Regards,
Ken Takata

David Odin

unread,
May 17, 2018, 3:42:14 PM5/17/18
to vim...@googlegroups.com, vim-an...@vim.org, vim...@vim.org, v...@vim.org, vim...@vim.org
On Thu, May 17, 2018 at 08:18:26PM +0200, Bram Moolenaar wrote:
>
> Hello Vim users!
>
> Announcing: Vim (Vi IMproved) version 8.1
>
>
Congrats!

--
<david...@forma3dev.fr>

Christian J. Robinson

unread,
May 17, 2018, 3:46:36 PM5/17/18
to vim...@vim.org
On Thu, 17 May 2018, Bram Moolenaar wrote:

> Announcing: Vim (Vi IMproved) version 8.1

Just FYI, v:version is incorrect for 8.1 (reports as 800), and
https://www.vim.org/version.txt is also out of date.

--
Christian J. Robinson <hep...@gmail.com> -- https://christianrobinson.name/
Other than that, Mrs. Lincoln, how was the play?

Gary Johnson

unread,
May 17, 2018, 3:52:24 PM5/17/18
to vim...@googlegroups.com
On 2018-05-17, Christian J. Robinson wrote:
> On Thu, 17 May 2018, Bram Moolenaar wrote:
>
> >Announcing: Vim (Vi IMproved) version 8.1
>
> Just FYI, v:version is incorrect for 8.1 (reports as 800), and
> https://www.vim.org/version.txt is also out of date.

It reports 801 for me.

Regards,
Gary

Christian J. Robinson

unread,
May 17, 2018, 4:18:48 PM5/17/18
to vim...@googlegroups.com
My mistake. I had to force a full rebuild and now v:version is
correct.

--
Christian J. Robinson <hep...@gmail.com> -- https://christianrobinson.name/
"That we occasionally violate our own stated moral code does not imply that
we are insincere in espousing that code."
-- Neal Stephenson, "The Diamond Age"

Bram Moolenaar

unread,
May 17, 2018, 5:41:28 PM5/17/18
to vim...@googlegroups.com, Christian J. Robinson, vim...@vim.org

Christian J. Robinson wrote:

> On Thu, 17 May 2018, Bram Moolenaar wrote:
>
> > Announcing: Vim (Vi IMproved) version 8.1
>
> Just FYI, v:version is incorrect for 8.1 (reports as 800), and

:echo v:version
801


> https://www.vim.org/version.txt is also out of date.

Will be updated at the first patch (which usually doesn't take long).

--
TERRY GILLIAM PLAYED: PATSY (ARTHUR'S TRUSTY STEED), THE GREEN KNIGHT
SOOTHSAYER, BRIDGEKEEPER, SIR GAWAIN (THE FIRST TO BE
KILLED BY THE RABBIT)

Bram Moolenaar

unread,
May 17, 2018, 5:54:40 PM5/17/18
to vim...@googlegroups.com, Ken Takata

Ken Takata wrote:

> 2018/5/18 Fri 3:18:50 UTC+9 Bram Moolenaar wrote:
> > Hello Vim users!
> >
> > Announcing: Vim (Vi IMproved) version 8.1
>
> Congratulations!
>
> However, Netrw doesn't work on 8.1.
> It seems that the patch 8.0.0002 was accidentally reverted and needs to be
> applied again.

Weird. I haven't found the commit where this happened. I did try to
install a newer version of netrw, found that it had a problem and rolled
it back by using what is in the git repository.

> (I think this mistake would have been easily found if you have
> released a beta version.)

No, the problem appears to be building the release itself.

> And I also found two small mistake in version8.txt:
>
> --- a/runtime/doc/version8.txt
> +++ b/runtime/doc/version8.txt
> @@ -22104,7 +22104,7 @@ Files: src/Makefile, src/option.c,
> Patch 8.0.1238
> Problem: Incremental search only shows one match.
> Solution: When 'incsearch' and 'hlsearch' are both set highlight all
> - matches. (haya14busa, itchyny closes #2198)
> + matches. (haya14busa, itchyny, closes #2198)
> Files: runtime/doc/options.txt, src/ex_getln.c, src/proto/search.pro,
> src/search.c, src/testdir/test_search.vim
>
> @@ -22595,7 +22595,7 @@ Solution: Remove bogus typedef.
> Files: src/os_macosx.m
>
> Patch 8.0.1316 (after 8.0.1312)
> -Problem: Build still fails on Mac. (chdiza)
> +Problem: Build still still fails on Mac. (chdiza)
> Solution: Remove another bogus typedef.
> Files: src/os_mac_conv.c
>
>
> The first one was my mistake, a comma was missing.
> The second one was changed by Dominique's patch, however the double "still"
> was intentional, I think.

I'll include this soon.

--
Communication is one of the most compli..., eh, well, it's hard.
You know what I mean. Not?

Yegappan Lakshmanan

unread,
May 17, 2018, 6:27:40 PM5/17/18
to vim_dev
Hi Bram,

On Thu, May 17, 2018 at 11:18 AM, Bram Moolenaar <Br...@moolenaar.net> wrote:
>
> Hello Vim users!
>
> Announcing: Vim (Vi IMproved) version 8.1
>
>
> This is a minor release with many small improvements and lots of bug
> fixes. The main new feature is the terminal window. I have put up a
> few screenshots on the Vim website:
> https://www.vim.org/vim-8.1-released.php
>
> Once you have installed Vim 8.1 you can find details about the changes
> since Vim 8.1 with:
> :help version8.1
> Or view it online:
> https://raw.githubusercontent.com/vim/vim/master/runtime/doc/version8.txt
>

The new quickfix features are not mentioned under ":help version8.1".
I will send a patch later with the list of new quickfix features.

- Yegappan

Ken Takata

unread,
May 17, 2018, 8:12:38 PM5/17/18
to vim_dev
Hi Bram,

2018/5/18 Fri 6:54:40 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > 2018/5/18 Fri 3:18:50 UTC+9 Bram Moolenaar wrote:
> > > Hello Vim users!
> > >
> > > Announcing: Vim (Vi IMproved) version 8.1
> >
> > Congratulations!
> >
> > However, Netrw doesn't work on 8.1.
> > It seems that the patch 8.0.0002 was accidentally reverted and needs to be
> > applied again.
>
> Weird. I haven't found the commit where this happened. I did try to
> install a newer version of netrw, found that it had a problem and rolled
> it back by using what is in the git repository.

I have found the commit:
https://github.com/vim/vim/commit/4697399e8c805325009351a2488e3da530d0af38

When you rolled back netrw from 162 to 156, you also reverted the patch
8.0.0002.


> > (I think this mistake would have been easily found if you have
> > released a beta version.)
>
> No, the problem appears to be building the release itself.

I don't think so. But even so, it would have been found by someone.
You released v7.4a.xxx and v7.4b.xxx before v7.4 and the method worked well,

Christian Brabandt

unread,
May 18, 2018, 2:51:28 AM5/18/18
to vim...@googlegroups.com, vim...@vim.org

On Do, 17 Mai 2018, L. A. Walsh wrote:

> It's not clear if this that binary is a 64-bit version ...
> 32-bit runs between 10-15% slower on 64-bit machines.

There are nightly 64 bit builds available at
https://github.com/vim/vim-win32-installer/releases

However, I doubt you'll notice a difference when running those versions.
After all it is an editor and not a bitcoin miner.

Best,
Christian
--
Fang jetzt zu leben an, und zähle jeden Tag als ein Leben für sich.
-- Lucius Annaeus Seneca (4-65 n.Chr.)

Christian Brabandt

unread,
May 18, 2018, 2:52:08 AM5/18/18
to vim...@vim.org, v...@vim.org

On Do, 17 Mai 2018, Bram Moolenaar wrote:

> Announcing: Vim (Vi IMproved) version 8.1

Congratulation.

Best,
Christian
--
Das Leben ist bezaubernd, man muß es nur durch die richtige Brille
sehen.
Frauen inspirieren uns zu großen Dingen - und hinden uns dann, sie
auszuführen.
-- Alexandre Dumas d.J.

Bram Moolenaar

unread,
May 18, 2018, 4:05:40 AM5/18/18
to vim...@googlegroups.com, Ken Takata

Ken Takata wrote:

> 2018/5/18 Fri 6:54:40 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > 2018/5/18 Fri 3:18:50 UTC+9 Bram Moolenaar wrote:
> > > > Hello Vim users!
> > > >
> > > > Announcing: Vim (Vi IMproved) version 8.1
> > >
> > > Congratulations!
> > >
> > > However, Netrw doesn't work on 8.1.
> > > It seems that the patch 8.0.0002 was accidentally reverted and needs to be
> > > applied again.
> >
> > Weird. I haven't found the commit where this happened. I did try to
> > install a newer version of netrw, found that it had a problem and rolled
> > it back by using what is in the git repository.
>
> I have found the commit:
> https://github.com/vim/vim/commit/4697399e8c805325009351a2488e3da530d0af38
>
> When you rolled back netrw from 162 to 156, you also reverted the patch
> 8.0.0002.

Oh, but that is long ago. Why didn't anybody complain that this didn't
work? Everybody using the github version would have run into this
problem.

I wonder if there are any other changes that got rolled back.

--
MICHAEL PALIN PLAYED: 1ST SOLDIER WITH A KEEN INTEREST IN BIRDS, DENNIS, MR
DUCK (A VILLAGE CARPENTER WHO IS ALMOST KEENER THAN
ANYONE ELSE TO BURN WITCHES), THREE-HEADED KNIGHT, SIR
GALAHAD, KING OF SWAMP CASTLE, BROTHER MAYNARD'S ROOMATE
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

Tony Mechelynck

unread,
May 18, 2018, 4:15:49 AM5/18/18
to vim_dev, vim-dev, v...@vim.org
On Fri, May 18, 2018 at 8:51 AM, Christian Brabandt <cbl...@256bit.org> wrote:
>
> On Do, 17 Mai 2018, Bram Moolenaar wrote:
>
>> Announcing: Vim (Vi IMproved) version 8.1
>
> Congratulation.
>
> Best,
> Christian

After moving, my phone & Internet line had been kept for a few days at
my old address. When getting back online (for Internet at least, and
AFAICT for incoming but not outgoing phone calls) I find Vim is now at
version/patchlevel 8.1.1. This is the best surprise (so far) I've had
to celebrate the move. Thanks Bram, congratulations, and long live to
Vim!

Best regards,
Tony.

Ni Va

unread,
May 18, 2018, 4:23:41 AM5/18/18
to vim_dev
Congratulations and many thanks Bram.

Christian Brabandt

unread,
May 18, 2018, 4:33:37 AM5/18/18
to vim...@googlegroups.com

On Fr, 18 Mai 2018, Bram Moolenaar wrote:

> Oh, but that is long ago. Why didn't anybody complain that this didn't
> work? Everybody using the github version would have run into this
> problem.
>
> I wonder if there are any other changes that got rolled back.

When you rolled back netrw, Vim was already at version 8.0.1390, so that
check
,----
| if v:version < 704 || !has("patch213")
`----

still returned true. However with Release 8.1, the check for patch 213
did start failing again.

Mit freundlichen Grüßen
Christian
--
Die Zensur ist das lebendige Geständnis der Großen, daß sie nur
verdummte Sklaven treten, aber keine freien Völker regieren können.
-- Johann Nepomuk Nestroy

Dominique Pellé

unread,
May 18, 2018, 4:40:42 AM5/18/18
to vim_dev
Bram Moolenaar <Br...@moolenaar.net> wrote:

> > When you rolled back netrw from 162 to 156, you also reverted the patch
> > 8.0.0002.

> Oh, but that is long ago. Why didn't anybody complain that this didn't
> work? Everybody using the github version would have run into this
> problem.

Nobody complained because it worked until the version number
was changed from 8.0.* to 8.1. This line in runtime/autoload/netrw.vim
was bad:

I'm guessing that this was wrong:

+if v:version < 704 || !has("patch213")
+ if !exists("s:needpatch213")
+ unsilent echomsg "***sorry*** this version of netrw requires vim v7.4
with patch 213"
+ endif

The call has("patch213") was true with vim-8.0.* (>= 8.0.123)
but became false with vim 8.1 causing the issue.
It was a time bomb waiting to happen.

I think that there is always a risk when we change from 8.x to 8.(x+1)
as it becomes the official release without feedback.
Can the process change? We had the same kind issue for
version 7.4 -> 8.0 and version 8.0 -> 8.1.

Regards
Dominique

Bram Moolenaar

unread,
May 18, 2018, 5:23:10 AM5/18/18
to vim...@googlegroups.com, Christian Brabandt

Christian wrote:

> On Fr, 18 Mai 2018, Bram Moolenaar wrote:
>
> > Oh, but that is long ago. Why didn't anybody complain that this didn't
> > work? Everybody using the github version would have run into this
> > problem.
> >
> > I wonder if there are any other changes that got rolled back.
>
> When you rolled back netrw, Vim was already at version 8.0.1390, so that
> check
> ,----
> | if v:version < 704 || !has("patch213")
> `----
>
> still returned true. However with Release 8.1, the check for patch 213
> did start failing again.

Ah, of course, patch213 existed in 8.0 by then, and nobody noticed the
check was actually wrong. I should not try to figure this out late at
night...

We should not have that kind of check, since it leads to problems like
this. I'll update the help for it.

--
A disclaimer for the disclaimer:
"and before I get a huge amount of complaints , I have no control over the
disclaimer at the end of this mail :-)" (Timothy Aldrich)

Tony Mechelynck

unread,
May 18, 2018, 6:06:42 AM5/18/18
to vim_dev, Christian Brabandt
On Fri, May 18, 2018 at 11:23 AM, Bram Moolenaar <Br...@moolenaar.net> wrote:
>
> Christian wrote:
>
>> On Fr, 18 Mai 2018, Bram Moolenaar wrote:
>>
>> > Oh, but that is long ago. Why didn't anybody complain that this didn't
>> > work? Everybody using the github version would have run into this
>> > problem.
>> >
>> > I wonder if there are any other changes that got rolled back.
>>
>> When you rolled back netrw, Vim was already at version 8.0.1390, so that
>> check
>> ,----
>> | if v:version < 704 || !has("patch213")
>> `----
>>
>> still returned true. However with Release 8.1, the check for patch 213
>> did start failing again.
>
> Ah, of course, patch213 existed in 8.0 by then, and nobody noticed the
> check was actually wrong. I should not try to figure this out late at
> night...
>
> We should not have that kind of check, since it leads to problems like
> this. I'll update the help for it.

The correct check is of course similar to what is already shown under
":help has-patch"; with the opposite truth logic it becomes

if version < 704 || (v:version == 704 && !has(patch213))

using "version" without v: in the first test to account for very old
Vim versions which did not yet know about v:version with the v:

Or, to keep the form used at |has-patch|,

if ! (version > 704 || (version == 704 && has(patch213)))

but in this case very old versions would still test both sides of the
||, even with short-circuit evaluation.

>
> --
> A disclaimer for the disclaimer:
> "and before I get a huge amount of complaints , I have no control over the
> disclaimer at the end of this mail :-)" (Timothy Aldrich)
>
> /// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
> /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
> \\\ an exciting new programming language -- http://www.Zimbu.org ///
> \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

Best regards,
Tony.

Diego Viola

unread,
May 19, 2018, 5:15:39 PM5/19/18
to vim_dev

Congratulations.

Can we have new colorschemes by default on the next Vim version please?

https://github.com/vim/vim/issues/1665

Reply all
Reply to author
Forward
0 new messages