Patch 8.0.0170

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0170 (after 8.0.0169) Summary:crash in channel test Problem:Channel test fails for using freed memory. Solution: Fix memory use in json_decode(). Files: src/json.c *** ../vim-8.0.0169/src/json.c 2017-01-10 19:44:14.594027155 +0100 --- src/json.c 2017-01-10 22:52:50.684

Re: test failures on macOS 10.12.2

2017-01-10 Fir de Conversatie Bram Moolenaar
Manuel Ortega wrote: > On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are > suddenly test failures: > > > VIMRUNTIME=../../runtime; export VIMRUNTIME; ../vim -f -u unix.vim -U > NONE --noplugin --not-a-term -U NONE -S r

Re: [vim/vim] Scripts named "build" are detected as bzl (#1340)

2017-01-10 Fir de Conversatie mossgary600 via vim_dev
On Tue, 1/10/17, Daniel Ge wrote: Subject: Re: [vim/vim] Scripts named "build" are detected as bzl (#1340) To: "vim/vim" Cc: "Subscribed" Date: Tuesday, January 10, 2017, 11:07 PM The same behavior is on MacOS because HFS defaults to case-in

Re: test failures on macOS 10.12.2

2017-01-10 Fir de Conversatie Dominique Pellé
Manuel Ortega wrote: > On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are > suddenly test failures: > > > VIMRUNTIME=../../runtime; export VIMRUNTIME; ../vim -f -u unix.vim -U NONE > --noplugin --not-a-term -U NONE -S run

Re: test failures on macOS 10.12.2

2017-01-10 Fir de Conversatie Manuel Ortega
On Tuesday, January 10, 2017 at 1:31:03 PM UTC-6, Manuel Ortega wrote: > On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are > suddenly test failures: > > > > VIMRUNTIME=../../runtime; export VIMRUNTIME;  ../vim -f  -u uni

test failures on macOS 10.12.2

2017-01-10 Fir de Conversatie Manuel Ortega
On macOS 10.12.2, with a fresh pull of the repo up to 8.0.169, there are suddenly test failures: VIMRUNTIME=../../runtime; export VIMRUNTIME; ../vim -f -u unix.vim -U NONE --noplugin --not-a-term -U NONE -S runtest.vim test_channel.vim Vim: Ca

Patch 8.0.0169

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0169 Summary:json_decode() may run out of stack space Problem:For complicated string json_decode() may run out of stack space. Solution: Change the recursive solution into an iterative solution. Files: src/json.c *** ../vim-8.0.0168/src/json.c 2017-01-10 15:15:32.878134

Patch 8.0.0168

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0168 Summary:not all float functionality is tested Problem:Still some float functionality is not covered by tests. Solution: Add more tests. (Dominique Pelle, closes #1364) Files: src/testdir/test_float_func.vim *** ../vim-8.0.0167/src/testdir/test_float_func.vim 201

Patch 8.0.0167

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0167 Problem:str2nr() and str2float() do not always work with negative values. Solution: Be more flexible about handling signs. (LemonBoy, closes #1332) Add more tests. Files: src/evalfunc.c, src/testdir/test_float_func.vim, src/testdir/test_functions.v

Patch 8.0.0166

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0166 Summary:JSON with a duplicate key gives an internal error Problem:JSON with a duplicate key gives an internal error. (Lcd) Solution: Give a normal error. Avoid an error when parsing JSON from a remote client fails. Files: src/evalfunc.c, src/json.c, src/c

Patch 8.0.0165

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0165 Problem:Ubsan warns for integer overflow. Solution: Swap two conditions. (Dominique Pelle) Files: src/regexp_nfa.c *** ../vim-8.0.0164/src/regexp_nfa.c2017-01-08 20:50:47.433486722 +0100 --- src/regexp_nfa.c2017-01-10 13:53:01.154397567 +0100 *** ***

Patch 8.0.0164

2017-01-10 Fir de Conversatie Bram Moolenaar
Patch 8.0.0164 Problem:Outdated and misplaced comments. Solution: Fix the comments. Files: src/charset.c, src/getchar.c, src/list.c, src/misc2.c, src/testdir/README.txt *** ../vim-8.0.0163/src/charset.c 2016-08-29 22:42:20.0 +0200 --- src/charset.c 2016

Re: [patch][doc] Fix description of strcharpart()

2017-01-10 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > The function strcharpart() uses character index instead of byte index. > Therefore "one byte" should be "one character", I think. Thanks! -- hundred-and-one symptoms of being an internet addict: 242. You turn down a better-paying job because it doesn't come with a free

[patch][doc] Fix description of strcharpart()

2017-01-10 Fir de Conversatie Ken Takata
Hi, The function strcharpart() uses character index instead of byte index. Therefore "one byte" should be "one character", I think. --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -7256,7 +7256,7 @@ strcharpart({src}, {start}[, {len}]) * Like |strpar