Mercurial > vim

comparison runtime/doc/channel.txt @ 10385:368468ef35cf

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/c0514bf4777a1d55f5785b3887c5686fd0bbe870 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Nov 17 14:50:09 2016 +0100 Updated runtime files.
author Christian Brabandt <cb@256bit.org>
date Thu, 17 Nov 2016 15:00:05 +0100
parents 169a62d5bcb9
children e664ee056a84
comparison
equal deleted inserted replaced
10384:54db4e2b88b3 10385:368468ef35cf
1 *channel.txt* For Vim version 8.0. Last change: 2016 Oct 27 1 *channel.txt* For Vim version 8.0. Last change: 2016 Nov 07
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
367 ["call", "setline", ["$", ["one", "two", "three"]]] ~ 367 ["call", "setline", ["$", ["one", "two", "three"]]] ~
368 368
369 ============================================================================== 369 ==============================================================================
370 6. Using a RAW or NL channel *channel-raw* 370 6. Using a RAW or NL channel *channel-raw*
371 371
372 If mode is RAW or NL then a message can be send like this: > 372 If mode is RAW or NL then a message can be sent like this: >
373 let response = ch_evalraw(channel, {string}) 373 let response = ch_evalraw(channel, {string})
374 374
375 The {string} is sent as-is. The response will be what can be read from the 375 The {string} is sent as-is. The response will be what can be read from the
376 channel right away. Since Vim doesn't know how to recognize the end of the 376 channel right away. Since Vim doesn't know how to recognize the end of the
377 message you need to take care of it yourself. The timeout applies for reading 377 message you need to take care of it yourself. The timeout applies for reading