Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319)

On Sun, 12/11/16, h_east wrote: Subject: Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319) To: "vim_dev" Cc: v...@noreply.github.com, vim-dev-git...@256bit.org,

Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

On Mon, 12/12/16, maximabrowning via vim_dev wrote: Subject: Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC To: vim_dev@googlegroups.com Date: Monday,

Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

On Mon, 12/12/16, itchyny wrote: Subject: Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC To: "vim_dev" Cc:

Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

On Monday, December 12, 2016 at 2:28:51 AM UTC+9, Bram Moolenaar wrote: > Ken Hamada wrote: > > > Hi list. I found a strange behavior of fillchars and StatusLine. > > > > vim -u NONE --cmd 'set fillchars=stl:\ ,stlnc:\ ' --cmd 'vnew' > > I set both stl and stlnc space so that I don't see any ^

Re: Questions about vim_iswordc() and vim_iswordp()

On Sun, 12/11/16, Ozaki Kiichi wrote: Subject: Re: Questions about vim_iswordc() and vim_iswordp() To: "vim_dev" Date: Sunday, December 11, 2016, 11:06 PM I updated patch.

Re: Questions about vim_iswordc() and vim_iswordp()

I updated patch. https://gist.github.com/ichizok/1be6efa8364777cf167003e2c5676d8f (This assumes [1], [2] is correct) * vim_iswordp_buf() uses vim_iswordc_buf() directly * add kword_test to test the results of vim_iswordc and vim_iswordp are matched, in case the of enc=utf-8 and 0 <= c < 0x1

Patch 8.0.0133

Patch 8.0.0133 Problem:"2;'(" causes ml_get errors in an empty buffer. (Dominique Pelle) Solution: Check the cursor line earlier. Files: src/ex_docmd.c, src/testdir/test_cmdline.vim *** ../vim-8.0.0132/src/ex_docmd.c 2016-11-15 21:16:46.750453046 +0100 --- src/ex_docmd.c

Re: [vim/vim] set complete ignores priority order (#1316)

Hi Bram, Ruben and list, 2016-12-12(Mon) 1:40:01 UTC+9 Ruben Gonzalez: > Sorry, I find the error, I was using also: > > set completeopt=menuone,noinsert > > But, If I use > > set completeopt=menuone,preview > > Works as expected, the problem was using menuone,noinsert or menuone,noselect >

Re: stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

Ken Hamada wrote: > Hi list. I found a strange behavior of fillchars and StatusLine. > > vim -u NONE --cmd 'set fillchars=stl:\ ,stlnc:\ ' --cmd 'vnew' > I set both stl and stlnc space so that I don't see any ^ or = characters in > the statusline. > But when I set the following highlights, Vim

stl, stlnc of fillchars are not always applied, depends on difference between StatusLine and StatusLineNC

Hi list. I found a strange behavior of fillchars and StatusLine. vim -u NONE --cmd 'set fillchars=stl:\ ,stlnc:\ ' --cmd 'vnew' I set both stl and stlnc space so that I don't see any ^ or = characters in the statusline. But when I set the following highlights, Vim draws the statusline of the

Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319)

On Sun, 12/11/16, vim-dev ML wrote: Subject: Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319) To: "vim/vim" Cc: "vim-dev ML" , "Your

Patch 8.0.0132

Patch 8.0.0132 (after 8.0.0131) Problem:Test fails because of using :finish. Solution: Change to return. Files: src/testdir/test_syntax.vim *** ../vim-8.0.0131/src/testdir/test_syntax.vim 2016-12-11 15:11:13.912466773 +0100 --- src/testdir/test_syntax.vim 2016-12-11

Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319)

Hi Lifepillar and list, 2016-12-11(Sun) 21:40:07 UTC+9 Lifepillar: > Thanks for the quick reply! I do not think that this is the correct fix, > though. According to the manual (:h i_CTRL-X_CTRL-V), when the pop-up menu > becomes visible after , pressing again behaves like > or . I'm fine

Re: [patch] improved test coverage (:syntime, :syntax list, :syntax completion)

Dominique wrote: > Attached patch improves test coverage for > the following items not currently covered > according to coveralls [1]: > - :syntime command > - :syntax list command > - :syntax completion > > I did not test ":syntax list @{cluster-name} described > at ":help :syn-list" as I did

Patch 8.0.0131

Patch 8.0.0131 Problem:Not enough test coverage for syntax commands. Solution: Add more tests. (Dominique Pelle) Files: src/testdir/test_syntax.vim *** ../vim-8.0.0130/src/testdir/test_syntax.vim 2016-04-20 12:30:11.0 +0200 --- src/testdir/test_syntax.vim 2016-12-11

Re: [vim/vim] Inconsistent behavior of when pattern is not found (#1319)

Hi Lifepillar, 2016-12-11(Sun) 18:52:20 UTC+9 Lifepillar: > Consider a buffer containing the text foobar. Type ofoo. > I would expect the pop-up menu to suggest foobar, but Vim stays in > command-line completion and does not show anything. I think that this is a > bug. I think so. How about

Re: [vim/vim] Problems with -std=c11 compilation (#664)

On Sun, 12/11/16, ouidacisneros via vim_dev wrote: Subject: Re: [vim/vim] Problems with -std=c11 compilation (#664) To: vim_dev@googlegroups.com Date: Sunday, December 11, 2016, 8:48 AM