Re: "a" . 1.1 become "a11"

2016-03-01 Fir de Conversatie mattn
On Wednesday, March 2, 2016 at 8:31:20 AM UTC+9, Tony Mechelynck wrote: > A Float cannot be used as a String, that's error E806. You can see it by > trying > :echo "a" . (0 + 1.1) > which forces 1.1 to be a Float. > Since 1.1, when concatenated to "a", cannot be a Float, then it must > be 1 .

Re: "a" . 1.1 become "a11"

2016-03-01 Fir de Conversatie Tony Mechelynck
A Float cannot be used as a String, that's error E806. You can see it by trying :echo "a" . (0 + 1.1) which forces 1.1 to be a Float. Since 1.1, when concatenated to "a", cannot be a Float, then it must be 1 . 1 (1 concatenated with 1) which is indeed 11. TL;DR: T'ain't a bug, it's a feature.

Patch to fix errors seen when building without FEAT_AUTOCMD

2016-03-01 Fir de Conversatie Yegappan Lakshmanan
Hi all, The attached patch fixes errors seen when building Vim without FEAT_AUTOCMD. - Yegappan -- -- 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 ---

Re: Patch 7.4.1464

2016-03-01 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: > Thanks. I prefer to make difference for default and 1 clearly. Thanks! -- "I've been teaching myself to play the piano for about 5 years and now write most of my songs on it, mainly because I can never find any paper." Jeff Lynne, ELO's greatest

Patch 7.4.1468

2016-03-01 Fir de Conversatie Bram Moolenaar
Patch 7.4.1468 Problem:Sort test doesn't test with "1" argument. Solution: Also test ignore-case sorting. (Yasuhiro Matsumoto) Files: src/testdir/test_sort.vim *** ../vim-7.4.1467/src/testdir/test_sort.vim 2016-02-29 22:05:16.841676901 +0100 --- src/testdir/test_sort.vim

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

2016-03-01 Fir de Conversatie Charles E Campbell
Christian Brabandt wrote: > Hi Charles! > > On Di, 01 Mär 2016, Charles E Campbell wrote: > >> This is a solution, but inadequate, I'm afraid. The right solution >> (now, for the 3rd time): use a vim with patch 1141, along with >> syntax/sh.vim v145. > I am afraid, your message does not make it

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

2016-03-01 Fir de Conversatie Christian Brabandt
Hi Charles! On Di, 01 Mär 2016, Charles E Campbell wrote: > Christian Brabandt wrote: > > > > I think, the problem is this line from sh.vim (distributed with vim): > > > > |syn region shCaseEsac matchgroup=shConditional start="\ > matchgroup=shConditional end="\" end="\"

Re: [vim] sh.vim incorrectly highlighting if/fi (#636)

2016-03-01 Fir de Conversatie Charles E Campbell
Christian Brabandt wrote: > > I think, the problem is this line from sh.vim (distributed with vim): > > |syn region shCaseEsac matchgroup=shConditional start="\ matchgroup=shConditional end="\" end="\" contains=@shLoopList | > > which matches the xcode-select command.

Re: Patch 7.4.1440

2016-03-01 Fir de Conversatie John Marriott
On 01-Mar-2016 8:05 AM, Bram Moolenaar wrote: Please try again after patch 7.4.1463. All good now thanks. -- -- 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] sh.vim incorrectly highlighting if/fi (#636)

2016-03-01 Fir de Conversatie Charles Campbell
mattn wrote: > > Could you please try below? > > |$ vim -u NONE -N your.sh :syntax on ... move cursor into `--install` > above ... :echo synIDattr(synID(line("."), col("."), 1), "name") | > > I get shOption. > > I get shOption. That's what --install is supposed to be highlighted as. More fully:

Re: Patch 7.4.1463

2016-03-01 Fir de Conversatie Ben Fritz
On Monday, February 29, 2016 at 2:38:47 PM UTC-6, Bram Moolenaar wrote: > Patch 7.4.1463 > Problem:Configure doesn't find isinf() and isnan() on some systems. > Solution: Use a configure check that includes math.h. Thanks, I confirm I can build both on my old Solaris system and on my more

Re: v:true == 1 but [v:true] != [1]

2016-03-01 Fir de Conversatie Nikolay Aleksandrovich Pavlov
2016-03-01 13:39 GMT+03:00 mattn : > On Tuesday, March 1, 2016 at 5:10:47 PM UTC+9, ZyX wrote: >> 2016-03-01 4:42 GMT+03:00 mattn : >> > Below is a patch to fix tv_equal. >> > >> > https://gist.github.com/mattn/fb486829628b39e371a7 >> >> Automatic type

Re: v:true == 1 but [v:true] != [1]

2016-03-01 Fir de Conversatie mattn
On Tuesday, March 1, 2016 at 5:10:47 PM UTC+9, ZyX wrote: > 2016-03-01 4:42 GMT+03:00 mattn : > > Below is a patch to fix tv_equal. > > > > https://gist.github.com/mattn/fb486829628b39e371a7 > > Automatic type conversions never worked when using lists, check [1] == > ["1"]. I

Re: 7.4.1457 test failure on OS X 10.11.3

2016-03-01 Fir de Conversatie Bram Moolenaar
Kazunobu Kuriyama wrote: > Unfortunately, I got the same experience that Manuel Ortega went through. > > Yesterday, I ran "make test" several times after pulling the patch into my > repo, and didn't see any failure with it. > > But today, I got it (FWIW, after pulling other new patches into

Re: v:true == 1 but [v:true] != [1]

2016-03-01 Fir de Conversatie Nikolay Aleksandrovich Pavlov
2016-03-01 4:42 GMT+03:00 mattn : > Below is a patch to fix tv_equal. > > https://gist.github.com/mattn/fb486829628b39e371a7 Automatic type conversions never worked when using lists, check [1] == ["1"]. I do not think this needs to be fixed, there is no way to compare lists