Mercurial > vim
diff runtime/doc/channel.txt @ 7992:78106b0f2c56
commit https://github.com/vim/vim/commit/cbebd4879cc78e670d79b2c57dc33d7b911c962a
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Feb 7 23:02:56 2016 +0100
Updated runtime files.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Sun, 07 Feb 2016 23:15:05 +0100 |
parents | 45ea5ebf3a98 |
children | abd64cf67bcf |
line wrap: on
line diff
--- a/runtime/doc/channel.txt +++ b/runtime/doc/channel.txt @@ -117,7 +117,9 @@ Once done with the channel, disconnect i Currently up to 10 channels can be in use at the same time. *E897* -When the channel can't be opened you will get an error message. +When the channel can't be opened you will get an error message. There is a +difference between MS-Windows and Unix: On Unix when the port doesn't exist +ch_open() fails quickly. On MS-Windows "waittime" applies. *E898* *E899* *E900* *E901* *E902* If there is an error reading or writing a channel it will be closed. @@ -169,6 +171,9 @@ channel does not have a handler the mess On read error or ch_close() the string "DETACH" is sent, if still possible. The channel will then be inactive. +It is also possible to use ch_sendraw() on a JSON or JS channel. The caller +is then completely responsible for correct encoding and decoding. + ============================================================================== 4. Vim commands *channel-commands* @@ -266,6 +271,8 @@ asynchronously: > This {string} can also be JSON, use |jsonencode()| to create it and |jsondecode()| to handle a received JSON message. +It is not possible to use |ch_sendexpr()| on a raw channel. + ============================================================================== 6. Job control *job-control*