Re: Vim 8.0 released!

On Monday, September 12, 2016 at 8:53:54 PM UTC+8, Bram Moolenaar wrote: > Hello Vim users! > > > Announcing: Vim (Vi IMproved) version 8.0 > > > This the first major Vim release in ten years. There are interesting > new features, many small improvements and lots of bug fixes. >

Possible problem when running a job immediately followed by a sleep

While I was trying to write some vim code for testing a (async) functionality for Neomake plugin, I've noticed the following scenario: - Having the following shell script (with errors): #!/bin/sh a='$var' foo( - And the next vim test code: function! StartJob() let g:job =

[patch] Trivial :help syn-iskeyword fix

Please see attached. Regards, Doug -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the

Re: [vim/vim] Cname for vim.org to point to www.vim.org (#1062)

Some browsers, including by default Firefox and SeaMonkey, will look up www.something.tld if something.tld isn't found. This feature can be disabled by means of a preference, however, so it may or may not be a problem for you. For me it isn't. Best regards, Tony. On Mon, Sep 12, 2016 at 11:10

Patch 8.0.0003

Patch 8.0.0003 Problem:getwinvar() returns wrong Value of boolean and number options, especially non big endian systems. (James McCoy) Solution: Cast the pointer to long or int. (closes #1060) Files: src/option.c, src/testdir/test_bufwintabinfo.vim ***

Re: Vim 8.0 released!

Christian Robinson wrote: > On Mon, 12 Sep 2016, Bram Moolenaar wrote: > > > Christian Robinson wrote: > > > >> I just updated. Things like ":intro" and ":version" show 8.0, but > >> ":echo v:version" still shows "704". > > > > If v:version says 704, then it's 7.4. > > Sounds like you are

Re: Vim 8.0 released!

On Mon, 12 Sep 2016, Christian J. Robinson wrote: On Mon, 12 Sep 2016, Bram Moolenaar wrote: Christian Robinson wrote: I just updated. Things like ":intro" and ":version" show 8.0, but ":echo v:version" still shows "704". If v:version says 704, then it's 7.4. Sounds like you are running

Re: Test_get_buf_options fails on ppc64

On Sep 12, 2016 10:36, "Bram Moolenaar" wrote: > > > Ismail Donmez wrote: > > > on openSUSE Linux PPC64 I see one failure with Test_get_buf_options: > > > > From test_bufwintabinfo.vim: > > Executing Test_get_buf_options() > > Executing Test_get_win_options() > > Executing

Re: Vim 8.0 released!

Christian Robinson wrote: > I just updated. Things like ":intro" and ":version" show 8.0, but > ":echo v:version" still shows "704". If v:version says 704, then it's 7.4. Sounds like you are running an older binary with newer runtime files. -- hundred-and-one symptoms of being an internet

Re: Vim 8.0 released!

On Mon, 12 Sep 2016, Bram Moolenaar wrote: Christian Robinson wrote: I just updated. Things like ":intro" and ":version" show 8.0, but ":echo v:version" still shows "704". If v:version says 704, then it's 7.4. Sounds like you are running an older binary with newer runtime files. I am

Re: Patch 8.0.0002

I wrote: > Patch 8.0.0002 > Problem:The netrw plugin does not work. > Solution: Make it accept version 8.0. > Files: runtime/autoload/netrw.vim Since this prevented editing directories, I have updated the Vim 8 distribution files to this patch level. -- Emacs is a nice OS - but it

Re: Vim 8.0 released!

skywind3000 wrote: > Bram Moolenaar wrote： > > Hello Vim users! > > > > > > Announcing: Vim (Vi IMproved) version 8.0 > > > > > > This the first major Vim release in ten years. There are interesting > > new features, many small improvements and lots of bug fixes. > > At last ! > Hope

Re: Vim 8.0 released!

I just updated. Things like ":intro" and ":version" show 8.0, but ":echo v:version" still shows "704". - Christian -- Christian J. Robinson Expecting the world to treat you fairly because you are a good person is a little like expecting the bull not to attack you

Re: Vim 8.0 released!

On 12 September 2016, Bram Moolenaar wrote: > > > Hello Vim users! > > > Announcing: Vim (Vi IMproved) version 8.0 [...] Congratulations! /lcd -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: Vim 8.0 released!

Bram Moolenaar wrote： > Hello Vim users! > > > Announcing: Vim (Vi IMproved) version 8.0 > > > This the first major Vim release in ten years. There are interesting > new features, many small improvements and lots of bug fixes. At last ! Hope package maintainers of debian / ubuntu can update

Re: Test_get_buf_options fails on ppc64

Ismail Donmez wrote: > on openSUSE Linux PPC64 I see one failure with Test_get_buf_options: > > From test_bufwintabinfo.vim: > Executing Test_get_buf_options() > Executing Test_get_win_options() > Executing Test_getbufwintabinfo() > Executed 3 tests > 1 FAILED: > Found errors in

Re: Patch 8.0.0002

I wrote: > Patch 8.0.0002 > Problem:The netrw plugin does not work. > Solution: Make it accept version 8.0. > Files: runtime/autoload/netrw.vim That's unfortunate. Didn't get caught in testing because the problem is triggered by the updated version number. I'll consider updating

Patch 8.0.0002

Patch 8.0.0002 Problem:The netrw plugin does not work. Solution: Make it accept version 8.0. Files: runtime/autoload/netrw.vim *** ../vim-8.0.0001/runtime/autoload/netrw.vim 2016-04-20 22:23:51.0 +0200 --- runtime/autoload/netrw.vim 2016-09-12 16:28:24.426361650 +0200

Test_get_buf_options fails on ppc64

Hi, on openSUSE Linux PPC64 I see one failure with Test_get_buf_options: >From test_bufwintabinfo.vim: Executing Test_get_buf_options() Executing Test_get_win_options() Executing Test_getbufwintabinfo() Executed 3 tests 1 FAILED: Found errors in Test_get_buf_options(): function

Patch 8.0.0001

Patch 8.0.0001 Problem:Intro screen still mentions version7. (Paul) Solution: Change it to version8. Files: src/version.c *** ../vim-8.0./src/version.c 2016-09-12 13:37:07.0 +0200 --- src/version.c 2016-09-12 16:09:53.005729023 +0200 *** *** 17,24

Re: [patch][win32] Remove old codes for Win9x etc.

Ken Takata wrote: > 2016/3/9 Wed 23:33:28 UTC+9 Ken Takata wrote: > > Hi Bram, > > > > 2016/3/9 Wed 19:03:00 UTC+9 Bram Moolenaar wrote: > > > Ken Takata wrote: > > > > > > > 2016/3/8 Tue 23:43:09 UTC+9 Ken Takata wrote: > > > > > Hi, > > > > > > > > > > As the next release will drop support

Re: [patch][win32] Remove old codes for Win9x etc.

Hi Bram, 2016/3/9 Wed 23:33:28 UTC+9 Ken Takata wrote: > Hi Bram, > > 2016/3/9 Wed 19:03:00 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > 2016/3/8 Tue 23:43:09 UTC+9 Ken Takata wrote: > > > > Hi, > > > > > > > > As the next release will drop support for old Windows before XP, we

Re: Vim 8.0 released!

Hi Bram and Vim developers and users! Congrats!! I'll continue to write a patch in the future :-) -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more

Vim 8.0 released!

Hello Vim users! Announcing: Vim (Vi IMproved) version 8.0 This the first major Vim release in ten years. There are interesting new features, many small improvements and lots of bug fixes. Among the new features are: - Asynchronous I/O support, channels, JSON - Jobs - Timers - Partials,

Re: Vim 7.4y ready for beta testing

Hi Bram, 2016/9/12 Mon 20:19:46 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > 2016/9/7 Wed 6:02:38 UTC+9 Bram Moolenaar wrote: > > > Hello Vim users! > > > > > > > > > Announcing: Vim (Vi IMproved) version 7.4y BETA > > > > > > > > > This is the second BETA release for Vim 8. Same

Patch 7.4.2367

Patch 7.4.2367 (after 7.4.2364) Problem:Test runner misses a comma. Solution: Add the comma. Files: src/testdir/runtest.vim *** ../vim-7.4.2366/src/testdir/runtest.vim 2016-09-11 16:48:46.936005143 +0200 --- src/testdir/runtest.vim 2016-09-12 13:29:37.718637773 +0200

Re: Patch 7.4.2364

Ozaki Kiichi wrote: > > ! let s:flaky = [ > > ! \ 'Test_reltime()', > > ! \ 'Test_nb_basic()', > > ! \ 'Test_communicate()' > > ! \ 'Test_pipe_through_sort_some()' > > ! \ ] > > There is a missing comma after 'Test_communicate()'. Thanks. Strange that this went

Re: Vim 7.4y ready for beta testing

Ken Takata wrote: > 2016/9/7 Wed 6:02:38 UTC+9 Bram Moolenaar wrote: > > Hello Vim users! > > > > > > Announcing: Vim (Vi IMproved) version 7.4y BETA > > > > > > This is the second BETA release for Vim 8. Same files as 7.4x but with > > a few more changes. > > > > Please report anything

Patch 7.4.2366

Patch 7.4.2366 Problem:MS-Windows gvim.exe does not have DirectX support. Solution: Add the DIRECTX to the script. Files: src/bigvim.bat *** ../vim-7.4.2365/src/bigvim.bat 2016-09-06 23:23:46.389460230 +0200 --- src/bigvim.bat 2016-09-12 13:17:03.373009260 +0200

Re: Vim 7.4y ready for beta testing

Hi Bram, 2016/9/7 Wed 6:02:38 UTC+9 Bram Moolenaar wrote: > Hello Vim users! > > > Announcing: Vim (Vi IMproved) version 7.4y BETA > > > This is the second BETA release for Vim 8. Same files as 7.4x but with > a few more changes. > > Please report anything that isn't right. That includes

Re: should sh.vim update both 'syn iskeyword' and 'iskeyword' for bash scripts?

Kevin Ushey wrote: > syntax/sh.vim currently has (from > https://github.com/vim/vim/blob/e1c8c7a6742be6072290f9aa54ae358060d9c42f/runtime/syntax/sh.vim#L91-L98): > > " set up the syntax-highlighting iskeyword > if has("patch-7.4.1142") > if exists("b:is_bash") > exe "syn iskeyword ".",-,:"

Re: Patch 7.4.2364

> ! let s:flaky = [ > ! \ 'Test_reltime()', > ! \ 'Test_nb_basic()', > ! \ 'Test_communicate()' > ! \ 'Test_pipe_through_sort_some()' > ! \ ] There is a missing comma after 'Test_communicate()'. -- -- You received this message from the "vim_dev" maillist. Do not

Patch 7.4.2365

Patch 7.4.2365 Problem:Needless line break. Confusing directory name. Solution: Remove line break. Prepend "../" to "tools". Files: Makefile, src/normal.c *** ../vim-7.4.2364/Makefile2016-09-06 22:06:31.317534196 +0200 --- Makefile2016-09-06 22:51:30.614231758 +0200

Re: [vim/vim] Impossible to pass non-UTF-8 strings from vim to Python 3 (#1053)

Am 2016-09-12 11:09, schrieb Björn Linse: On Monday, September 12, 2016 at 10:57:39 AM UTC+2, Christian Brabandt wrote: On So, 11 Sep 2016, Björn Linse wrote: > On Sunday, September 11, 2016 at 6:14:14 PM UTC+2, Björn Linse wrote: > > 615351832d75df3dfbc3f22694e675583e0b325d > BTW, something is

Re: [patch] A small correction to version8.txt

Kazunobu Kuriyama wrote: > The attached patch is very tiny and self-explanatory. Please give it a > glance. Thanks. -- hundred-and-one symptoms of being an internet addict: 239. You think "surfing" is something you do on dry land. /// Bram Moolenaar -- b...@moolenaar.net --

should sh.vim update both 'syn iskeyword' and 'iskeyword' for bash scripts?

syntax/sh.vim currently has (from https://github.com/vim/vim/blob/e1c8c7a6742be6072290f9aa54ae358060d9c42f/runtime/syntax/sh.vim#L91-L98): " set up the syntax-highlighting iskeyword if has("patch-7.4.1142") if exists("b:is_bash") exe "syn iskeyword ".",-,:" else exe "syn iskeyword ".",-"

[patch] A small correction to version8.txt

Hi Bram, The attached patch is very tiny and self-explanatory. Please give it a glance. Thanks, Kazunobu -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit

Re: [vim/vim] Impossible to pass non-UTF-8 strings from vim to Python 3 (#1053)

On Monday, September 12, 2016 at 10:57:39 AM UTC+2, Christian Brabandt wrote: > Hi Björn! > > On So, 11 Sep 2016, Björn Linse wrote: > > > On Sunday, September 11, 2016 at 6:14:14 PM UTC+2, Björn Linse wrote: > > > 615351832d75df3dfbc3f22694e675583e0b325d > > BTW, something is wrong with the

Re: [vim/vim] Impossible to pass non-UTF-8 strings from vim to Python 3 (#1053)

Hi Björn! On So, 11 Sep 2016, Björn Linse wrote: > On Sunday, September 11, 2016 at 6:14:14 PM UTC+2, Björn Linse wrote: > > 615351832d75df3dfbc3f22694e675583e0b325d > BTW, something is wrong with the github <-> vim-dev bridge, this > comment (and the edited version with the correct link below)