Patch: Used function arguments marked as unused

2016-03-02 Fir de Conversatie Yegappan Lakshmanan
Hi, Several function parameters which are used in the function are incorrectly marked as unused. The attached patch fixes this. - 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, vis

[PATCH] escaping CSI for hangulinput

2016-03-02 Fir de Conversatie SungHyun Nam
Hello, if utf-8 encoding is used, converted string can include CSI. Thanks, namsh diff --git a/src/ui.c b/src/ui.c index be5d8c5..0f6502e 100644 --- a/src/ui.c +++ b/src/ui.c @@ -1691,8 +1691,16 @@ push_raw_key(char_u *s, int len) if (tmpbuf != NULL) s = tmpbuf; -while (len--)

Re: [if_perl][patch] Improve I/O integration

2016-03-02 Fir de Conversatie Christian J. Robinson
I've been using this patch for a while. It seems stable, and it's a needed change to the Perl interface. Bram, any chance of it being included? On Fri, Jan 22, 2016 at 11:30 AM, Damien wrote: > Hi Christian > > Le Fri, Jan 22, 2016 at 10:40:04AM -0700, Christian J. Robinson a écrit : > > On Fri,

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

2016-03-02 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: > Below is a patch to fix tv_equal. > > https://gist.github.com/mattn/fb486829628b39e371a7 Doesn't work when types are a dict and a list, for example. To make it consistent it should also work for v:null and 0. And v:none and 0. Not sure if that is an improvement tho

Re: [vim] two FEAT_FLOAT fixes (#667)

2016-03-02 Fir de Conversatie Bram Moolenaar
John Marriott wrote: > On 01-Mar-2016 9:13 AM, Bram Moolenaar (Vim Github Repository) wrote: > > > > Nick Owens wrote: > > > > > my vim port has no FEAT_FLOAT currently, so these helped fix my build. > > > > > > the moved define in json.c fixes gcc -Werror -Wunused-variable. > > > You can view, c

Patch 7.4.1474

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1474 Problem:Compiler warnings without the float feature. Solution: Move #ifdefs. (John Marriott) Files: src/eval.c *** ../vim-7.4.1473/src/eval.c 2016-02-29 23:12:44.210899417 +0100 --- src/eval.c 2016-03-02 22:14:53.125445524 +0100 *** *** 3152,3159

Patch 7.4.1473

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1473 Problem:Can't build without the autocommand feature. Solution: Add #ifdefs. (Yegappan Lakshmanan) Files: src/edit.c, src/main.c, src/syntax.c *** ../vim-7.4.1472/src/edit.c 2016-02-27 18:13:05.224593236 +0100 --- src/edit.c 2016-03-02 21:43:26.457067442 +0100

Re: Patch to fix errors seen when building without FEAT_AUTOCMD

2016-03-02 Fir de Conversatie Bram Moolenaar
Yegappan Lakshmanan wrote: > The attached patch fixes errors seen when building Vim without > FEAT_AUTOCMD. Thanks! -- If all you have is a hammer, everything looks like a nail. When your hammer is C++, everything begins to look like a thumb. -- Steve Hoflich, comp.lang

Patch 7.4.1472

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1472 Problem:Coverity warning for not using return value. Solution: Add "(void)". Files: src/os_unix.c *** ../vim-7.4.1471/src/os_unix.c 2016-02-29 12:52:35.478910442 +0100 --- src/os_unix.c 2016-03-02 21:19:01.624489586 +0100 *** *** 5235,5243

Patch 7.4.1471

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1471 Problem:Missing out-of-memory check. And Coverity warning. Solution: Bail out when msg is NULL. Files: src/channel.c *** ../vim-7.4.1470/src/channel.c 2016-03-02 21:09:28.670516946 +0100 --- src/channel.c 2016-03-02 21:15:00.111028733 +0100 ***

Re: "a" . 1.1 become "a11"

2016-03-02 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: > No need to handle want_string, I think. > > https://gist.github.com/mattn/7192570202d96e5f8539 I think that turning something that gives a result into something that produces an error is not useful. -- I used to wonder about the meaning of life. But I looked it up

Patch 7.4.1470

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1470 Problem:Coverity reports missing restore. Solution: Move json_encode() call up. Files: src/channel.c *** ../vim-7.4.1469/src/channel.c 2016-03-02 20:48:43.835501284 +0100 --- src/channel.c 2016-03-02 21:07:24.391826045 +0100 *** *** 1551,1572 ***

Patch 7.4.1469

2016-03-02 Fir de Conversatie Bram Moolenaar
Patch 7.4.1469 Problem:Channel test sometimes fails, especially on OS/X. (Kazunobu Kuriyama) Solution: Change the && into ||, call getsockopt() in more situations. (Ozaki Kiichi) Files: src/channel.c *** ../vim-7.4.1468/src/channel.c 2016-02-29 23:03:19.6

Re: 7.4.1457 test failure on OS X 10.11.3

2016-03-02 Fir de Conversatie Bram Moolenaar
Ozaki kiichi wrote: > I could reproduce this error after many trials. > But I encountered similar kind of failures a few time in also > v7.5.1456 test_channel. > > In my case, "write failed" is caused by "Broken pipe". (confirmed by > adding log message) This means that process had exited from w

Re: [patch] fix channel_open() error handling

2016-03-02 Fir de Conversatie Kazunobu Kuriyama
It's your view. >From my point of view, the description of the manual appeared to be vague. That was why I actually examined what value was returned by select() when connect() failed and errno was set to EINPROGRESS. I wrote that in the same email that you just quoted. Could you prove that zero

Re: [vim] two FEAT_FLOAT fixes (#667)

2016-03-02 Fir de Conversatie John Marriott
On 01-Mar-2016 9:13 AM, Bram Moolenaar (Vim Github Repository) wrote: Nick Owens wrote: > my vim port has no FEAT_FLOAT currently, so these helped fix my build. > > the moved define in json.c fixes gcc -Werror -Wunused-variable. > You can view, comment on, or merge this pull request online at:

Re: [patch] fix channel_open() error handling

2016-03-02 Fir de Conversatie Ozaki Kiichi
> In the section "Non-blocking connect" of the OS X manual page tcp(4), the > description about possible return values of select() is not clearly given for > the case in question. I think that sentence does not negate the meaning of the return value of select() (i.e. the number of ready descrip

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

2016-03-02 Fir de Conversatie Christian Brabandt
Hi Charles! On Di, 01 Mär 2016, Charles E Campbell wrote: > Has this been a vim bugtracker issue? Yes, basically all mails from vim-dev-git...@256bit.org are redirects from github and are mirrored to vim-dev. You can see it also in the subject which contains the repository in brackets ([vim])

Re: 7.4.1457 test failure on OS X 10.11.3

2016-03-02 Fir de Conversatie Ozaki Kiichi
I could reproduce this error after many trials. But I encountered similar kind of failures a few time in also v7.5.1456 test_channel. In my case, "write failed" is caused by "Broken pipe". (confirmed by adding log message) This means that process had exited from while loop* (not by 'return NULL'

Re: "a" . 1.1 become "a11"

2016-03-02 Fir de Conversatie LCD 47
On 2 March 2016, 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 . 1 (1 concatenated with 1) which

Re: [gtk3] Cursor drawing problems

2016-03-02 Fir de Conversatie Kazunobu Kuriyama
Then, that's a known issue. I've been looking into it. If the cursor issue matters to you, please use default gtk2 gui. If you still want to use gtk3 gui, how about adding the following to your .vimrc? let &gcr=&gcr . ",a:blinkon0" Thank you for your report, Kazunobu 2016-03-02 17:31 GMT+09:0

Re: [gtk3] Cursor drawing problems

2016-03-02 Fir de Conversatie Ismail Donmez
Kazunobu Kuriyama gmail.com> writes: > > > That was the case where you started gvim with "-u NONE -U NONE" or something like that and then stopped the blink, wasn't that? > Or, do you raise another issue? Ah, should be the same issue since I turn off cursor blink off indeed. -- -- You rece

Re: [gtk3] Cursor drawing problems

2016-03-02 Fir de Conversatie Kazunobu Kuriyama
That was the case where you started gvim with "-u NONE -U NONE" or something like that and then stopped the blink, wasn't that? Or, do you raise another issue? Regards, Kazunobu 2016-03-02 17:07 GMT+09:00 Ismail Donmez : > Hi, > > I tried the gtk3 gui again and I can move the cursor up and down

Re: Compiling with Python 3.5.1 on Windows

2016-03-02 Fir de Conversatie Axel Bender
Oh man! *SCHÄM* Thanks, and sorry for the noise... -- -- 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 subsc

Re: Compiling with Python 3.5.1 on Windows

2016-03-02 Fir de Conversatie Axel Bender
Oh man! *SCHÄHM* Thanks, and sorry for the noise... -- -- 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 subs

[gtk3] Cursor drawing problems

2016-03-02 Fir de Conversatie Ismail Donmez
Hi, I tried the gtk3 gui again and I can move the cursor up and down just fine but when I try to move the cursor left or right the cursor stays put but I can see the column number changes in the modeline so looks like the gui just fails to refresh the cursor position. This is on Linux x86-64 w

Re: Compiling with Python 3.5.1 on Windows

2016-03-02 Fir de Conversatie Christian Brabandt
Am 2016-03-02 09:02, schrieb Axel Bender: Windows 7 64-bit, MinGW 64, Python 3.5.1 in "d:\tools\python3" w/o Python 2 I don't get vim to work with Python 3.5.1 here. Python 2 is installed, but not enabled vim-wise. What am I doing wrong? Changes --- 1) src/make_cyg_ming.mak FEATURES=BIG PY

test_channel randomly fail

2016-03-02 Fir de Conversatie Ismail Donmez
Hi, On multiple versions of openSUSE Linux test_channel.vim randomly fails with: From test_channel.vim: Found errors in Test_close_handle(): function Test_close_handle[2]..3_run_server[44]..3_close_handle line 4: Expected 'what?' but got '' Found errors in Test_unlet_handle(): function Test

Compiling with Python 3.5.1 on Windows

2016-03-02 Fir de Conversatie Axel Bender
Windows 7 64-bit, MinGW 64, Python 3.5.1 in "d:\tools\python3" w/o Python 2 I don't get vim to work with Python 3.5.1 here. Python 2 is installed, but not enabled vim-wise. What am I doing wrong? Changes --- 1) src/make_cyg_ming.mak FEATURES=BIG PYTHON_VER=35 2) src/make_ming.mak PYTHON3=d:/t