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

On Tue, 12/13/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 Tuesday, December 13, 2016 at 1:26:30 AM UTC+9, Ozaki Kiichi wrote: > It is better to add it for an unit test. > > maka -C src test_fillchars Thank you for your notice, it's surely useful. Here is the latest patch. https://gist.github.com/itchyny/936f5c7e7f6396bf2f6afbe246206d47 Regards,

Re: [vim/vim] gtk3 gui substantially slower than gtk2 (#1199)

On Tue, 12/13/16, Matěj Cepl wrote: Subject: Re: [vim/vim] gtk3 gui substantially slower than gtk2 (#1199) To: "vim/vim" Date: Tuesday, December 13, 2016, 2:12 AM This seemed to get quite

Re: [vim/vim] Add v:argv variable (#1322)

* Gary Johnson [2016-12-13 01:45]: > argc() and argv() aren't sufficient? No. These functions work with *files* in the argument list of the current window. -- Dmitri Vereshchagin -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your

Re: Questions about vim_iswordc() and vim_iswordp()

On Mon, 12/12/16, Ozaki Kiichi wrote: Subject: Re: Questions about vim_iswordc() and vim_iswordp() To: "vim_dev" Cc: gclient.g...@gmail.com Date: Monday, December 12, 2016, 11:59 PM > They

Re: [vim/vim] Add v:argv variable (#1322)

On 2016-12-12, Dmitri Vereshchagin wrote: > It may be useful to have access to the command line arguments as a List stored > in v:argv variable. For example one may use it to check if Vim was invoked > without any arguments and open file browser automatically > > " ~/.vim/after/plugin/netrw.vim >

Re: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

Dominique wrote: > In Vim main help page (runtime/doc/help.txt), > there is a link |pi_logipat.txt| which is broken. > > Fixed in attached patch. Thanks! -- In a world without walls and borders, who needs windows and gates? /// Bram Moolenaar -- b...@moolenaar.net --

Re: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

Charles E Campbell wrote: > Dominique Pellé wrote: >> Hi >> >> In Vim main help page (runtime/doc/help.txt), >> there is a link |pi_logipat.txt| which is broken. >> >> Fixed in attached patch. >> > Thank you, Dominique -- I'll include that change. It is a leftover from > its incorporation as a

Re: Questions about vim_iswordc() and vim_iswordp()

> They should both respect 'iskeyword' for characters up to 255. > So it looks like vim_iswordp() needs to be fixed. > Thank you. OK, my above patch has reflected this fix. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are

Re: [patch] broken link pi_logipat.txt in runtime/doc/help.txt

Dominique Pellé wrote: > Hi > > In Vim main help page (runtime/doc/help.txt), > there is a link |pi_logipat.txt| which is broken. > > Fixed in attached patch. > Thank you, Dominique -- I'll include that change. It is a leftover from its incorporation as a part of vim. Chip Campbell -- -- You

[patch] improved completion of :syntax command

Hi Attached patch adds completion for: :syntax spell :syntax sync Regards Dominique -- -- 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

[patch] broken link pi_logipat.txt in runtime/doc/help.txt

Hi In Vim main help page (runtime/doc/help.txt), there is a link |pi_logipat.txt| which is broken. Fixed in attached patch. Regards Dominique -- -- 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

Re: Questions about vim_iswordc() and vim_iswordp()

Ozaki Kiichi wrote: > > when c == 0xA0, p == "\xC2\xA0", and 'iskeyword' includes 160 > > > > (e.g. iskeyword=@,48-57,_,128-167,224-235 (default on windows)) > > > > then: vim_iswordc(c) == 1, but vim_iswordp(p) == 0. > > After all, in the above case, should vim_iswordc(c) and vim_iswordp(p)

Re: Questions about vim_iswordc() and vim_iswordp()

> when c == 0xA0, p == "\xC2\xA0", and 'iskeyword' includes 160 > > (e.g. iskeyword=@,48-57,_,128-167,224-235 (default on windows)) > > then: vim_iswordc(c) == 1, but vim_iswordp(p) == 0. After all, in the above case, should vim_iswordc(c) and vim_iswordp(p) be whether TRUE or FALSE? -- --

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

> Sorry, there's no need to add the test in Makefile because I added into > test_alot.vim. I fixed the patch. It is better to add it for an unit test. maka -C src test_fillchars -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you

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

> Thank you Bram. I've got the point. > How about this patch? > I noticed the note in syntax.txt but still believe that the patch solves the > strange behavior > that most people will not configure what's going on until look into the > source code. > Sorry, there's no need to add the test in

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

Hi All, 2016-12-12(Mon) 21:58:29 UTC+9 Lifepillar: > I think noinsert or noselect is ignored only when completeopt includes menu > instead of menuone. > > > That would be more acceptable for me, too. My plugin requires menuone, so it > would not be affected. Hmm, Your requires item is