rneovim.git/src/nvim/msgpack_rpc, branch v0.4.3

Remove excess

2019-09-12T02:27:45+00:00

rename: SplitEvent => MulticastEvent #10989

2019-09-11T22:39:23+00:00

"Multicast" is perhaps a more conventional name for the concept.
"One-shot" is the conventional name for how the event is (currently)
scheduled.

rpc: allow handling of nvim_ui_try_resize at the pager

2019-09-08T13:24:14+00:00

This makes external UI behave consistenly with TUI w.r.t resizes.
Which will be needed anyway as TUI will use the external UI protocol
soon.

pvs/V1037: two case branches doing the same thing (#10527)

2019-07-18T01:12:45+00:00

rename: FUNC_API_ASYNC => FUNC_API_FAST

2019-06-30T09:33:01+00:00

api: allow nvim_buf_attach from lua using callbacks

2019-06-04T11:45:20+00:00

build: fix some warnings

2019-06-02T22:21:20+00:00

    ../src/nvim/event/rstream.c:119:44: warning: format specifies type 'void *' but the argument has type 'Stream *' (aka 'struct stream *') [-Wformat-pedantic]
          DLOG("Closing Stream (%p): %s (%s)", stream,
                                ~~             ^~~~~~
    ../src/nvim/event/stream.c:95:30: warning: format specifies type 'void *' but the argument has type 'Stream *' (aka 'struct stream *') [-Wformat-pedantic]
      DLOG("closing Stream: %p", stream);
                            ~~   ^~~~~~
    ../src/nvim/msgpack_rpc/channel.c:71:72: warning: format specifies type 'void *' but the argument has type 'Stream *' (aka 'struct stream *') [-Wformat-pedantic]
        DLOG("rpc ch %" PRIu64 " in-stream=%p out-stream=%p", channel->id, in, out);
                                           ~~                              ^~
    ../src/nvim/msgpack_rpc/channel.c:71:76: warning: format specifies type 'void *' but the argument has type 'Stream *' (aka 'struct stream *') [-Wformat-pedantic]
        DLOG("rpc ch %" PRIu64 " in-stream=%p out-stream=%p", channel->id, in, out);
                                                         ~~                    ^~~
    ../src/nvim/msgpack_rpc/channel.c:226:28: warning: format specifies type 'void *' but the argument has type 'Stream *' (aka 'struct stream *') [-Wformat-pedantic]
           channel->id, count, stream);
                               ^~~~~~

messages: use proper multiline error message for rpcrequest and API wrappers

2019-05-26T13:42:16+00:00

API: emit nvim_error_event on failed async request

2019-04-13T15:07:58+00:00

We already do this for _invalid_ async requests #9300.
Now we also do it for failed invocation of valid requests.

RPC: conform message-id type to msgpack-RPC spec

2019-04-12T00:31:46+00:00

According to [MessagePack RPC specification](https://github.com/msgpack-rpc/msgpack-rpc),
message ID must be 32-bit unsigned integer. But Neovim implementation
uses uint64_t instead of uint32_t. This can have wrong results in the
case of large ids or a malformed request, for example:

    Actual response:   [1,18446744073709551615,[1,"Message is not an array"],null]
    Expected response: [1,4294967295,[1,"Message is not an array"],null]

The issue does not affect RPC clients written in dynamically-typed
languages like Python. Wrong type of sequence id number breaks RPC
clients written statically typed languages like C/C++/Golang: all of
them expect uint32_t as message id.
Examples:
  https://github.com/msgpack-rpc/msgpack-rpc-cpp/blob/11268ba2be5954ddbb2b7676c7da576985e45cfc/src/msgpack/rpc/protocol.h#L27
  https://github.com/ugorji/go/blob/master/codec/msgpack.go#L993

closes #8850