Re: [proposal] new 'cursorlinenr' option

2016-11-26 Fir de Conversatie Ozaki Kiichi
I updated; changed type of 'cursorlinenr' to number. https://gist.github.com/ichizok/8d016c1e4c791499d092 And added test. https://gist.github.com/ichizok/aa54ecfe8aa7c94ce6711b940de16453 * which requires https://groups.google.com/forum/#!topic/vim_dev/tzNKP7EDWYI -- -- You received this

Patch 8.0.0104

2016-11-26 Fir de Conversatie Bram Moolenaar
Patch 8.0.0104 Problem:Value of 'thesaurus' option not checked properly. Solution: Add P_NDNAME flag. (Daisuke Suzuki) Files: src/option.c, src/testdir/test_options.vim *** ../vim-8.0.0103/src/option.c2016-11-25 22:04:09.607397081 +0100 --- src/option.c2016-11-26

Re: "ch_read()" couldn't tell the difference between "not enough message" and "a empty line"

2016-11-26 Fir de Conversatie Bram Moolenaar
Skywind wrote: > Bram Moolenaar wrote： > > > This will not break the plugins, and will make ch_read better. > > > It could be used in a timer for congestion control manually. > > > > That changes what you get back, that is a bit strange. > > How about adding a function that returns whether

Re: [PATCH] Incorrect cursor position on a long wrapped-line

2016-11-26 Fir de Conversatie h_east
Hi Kiichi, 2016-11-27(Sun) 0:09:20 UTC+9 Ozaki Kiichi: > https://gist.github.com/ichizok/4d177e3bf8cc9d47d47243577c8d847b > > * add test_number.vim > * separate some functions from test_breakindent.vim and add view.vim I think that file name and function names that can be used with the whole

Re: [PATCH] Incorrect cursor position on a long wrapped-line

2016-11-26 Fir de Conversatie Ozaki Kiichi
https://gist.github.com/ichizok/4d177e3bf8cc9d47d47243577c8d847b * add test_number.vim * separate some functions from test_breakindent.vim and add view.vim * change to easily visible expected values of tests in test_breakindent.vim Thank you. -- -- You received this message from the

Re: "ch_read()" couldn't tell the difference between "not enough message" and "a empty line"

2016-11-26 Fir de Conversatie skywind3000
Bram Moolenaar wrote： > > This will not break the plugins, and will make ch_read better. > > It could be used in a timer for congestion control manually. > > That changes what you get back, that is a bit strange. > How about adding a function that returns whether there is something to > read?

Patch 8.0.0103

2016-11-26 Fir de Conversatie Bram Moolenaar
Patch 8.0.0103 Problem:May not process channel readahead. (skywind) Solution: If there is readahead don't block on input. Files: src/channel.c, src/proto/channel.pro, src/os_unix.c, src/os_win32.c, src/misc2.c *** ../vim-8.0.0102/src/channel.c 2016-11-24

Re: "ch_read()" couldn't tell the difference between "not enough message" and "a empty line"

2016-11-26 Fir de Conversatie Bram Moolenaar
Skywind wrote: > What about provide an option "nl" in ch_read to make it better ? > > :call ch_read(mych, {"timeout": 0, "nl":1}) > > returns "abc\n" for a line "abc" > returns "\n" for an empty line > returns "" for not enough data > > This will not break the plugins, and will make ch_read

Re: Patch 8.0.0097

2016-11-26 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > 2016/11/25 Fri 1:23:12 UTC+9 Bram Moolenaar wrote: > > Patch 8.0.0097 > > Problem:When a channel callback consumes a lot of time Vim becomes > > unresponsive. (skywind) > > Solution: Bail out of checking channel readahead after 100 msec. > > Files:

Re: "ch_read()" couldn't tell the difference between "not enough message" and "a empty line"

2016-11-26 Fir de Conversatie Bram Moolenaar
Skywind wrote: > Thanks for the patch, > > I wrote a test : > (benchjob.vim for starting job, benchjob.py for printing 8 lines) > > --- > benchjob.vim: > > function! MyCallback(job, text) > " make cpu a little busy > for i in range(100) >