Kazunobu Kuriyama wrote:
> Looks you are trying to simplify the issue too much.
>
> Your argument looks good for utilities such as grep, tail, cut and so on.
>
> However, Vim (or any other programs having UI which is driven by events) is
> different from them in that, while Vim is made busy
On 10/18/2016 08:27 AM, Brad King wrote:
> On 10/17/2016 04:45 PM, Bram Moolenaar wrote:
>> Thanks. I suppose that's the best way to do it.
>
> Great. Here is a revised patch.
Ping.
Thanks,
-Brad
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply
Skywind wrote:
> Bram Moolenaar wrote:
> > Patch 8.0.0105
> > Problem:When using ch_read() with zero timeout, can't tell the
> > difference
> > between reading an empty line and nothing available.
> > Solution: Add ch_canread().
> > Files: src/evalfunc.c, src/channel.c,
Dominique wrote:
> Attached patch fixes a typo in runtime/doc/channel.txt
Thanks!
--
Creating the world with Emacs: M-x let-there-be-light
Creating the world with Vim: :make world
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote
skywind3000 wrote:
> I can sleep longer in timerjob.py, but I can't add a single sleep if I start
> grep as a job. And I can't decide how long should I sleep to avoid dropping.
latest channel.txt said:
Note that if the job exits before you read the output, the output may be lost.
This depends on
skywind3000 wrote:
> we can see:
>
> 1. there is a "sleep" in the parent process, parent works slower than child.
>
> 2. calling "write" block the child process successfully when pipe is full
> (4096 bytes on linux by default). The child process does not exit immediately.
>
> 3. 10 seconds
2016-11-30 19:06 GMT+09:00 skywind3000 :
> skywind3000 wrote:
>
> > we can see:
> >
> > 1. there is a "sleep" in the parent process, parent works slower than
> child.
> >
> > 2. calling "write" block the child process successfully when pipe is
> full (4096 bytes on linux by
Hi Kiichi and list,
2016-12-1(Thu) 12:03:09 UTC+9 Ozaki Kiichi:
> I updated test patch; modified some test-function names.
>
> https://gist.github.com/ichizok/4d177e3bf8cc9d47d47243577c8d847b
>
> @h_east:
>
> > I think that file name and function names that can be used with the whole
> > test
Bram Moolenaar wrote:
> When writing the test I also had problems with messages being dropped.
> I thought that adding a close callback should fix it, but perhaps there
> is another situation where they are still dropped.
>
> Can you enable the channel log and see where the messages are dropped?
I updated test patch; modified some test-function names.
https://gist.github.com/ichizok/4d177e3bf8cc9d47d47243577c8d847b
@h_east:
> I think that file name and function names that can be used with the whole
> test script should be named accordingly. Maybe we need a prefix?
Hmm. like
10 matches
Mail list logo