From 23a3e58f02e37ed5c6f8fa1f4758d0ebe1aed8d3 Mon Sep 17 00:00:00 2001 From: "Justin M. Keyes" Date: Mon, 13 Jun 2016 02:11:12 -0400 Subject: doc: msgpack_rpc: De-emphasize the transport protocol. Tighten our jargon, avoid mentioning "msgpack" everywhere we mention the RPC API. Prefer "RPC API" when speaking about the remote API. Though it's conceivable that we may one day support some protocol other than msgpack, that isn't relevant to most of our discussion of the API, including this document. The file name msgpack_rpc.txt is preserved to avoid totally breaking URLs. --- runtime/doc/api.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'runtime/doc/api.txt') diff --git a/runtime/doc/api.txt b/runtime/doc/api.txt index ca79465e0d..c35c393c8b 100644 --- a/runtime/doc/api.txt +++ b/runtime/doc/api.txt @@ -14,7 +14,7 @@ The C API of Nvim *nvim-api* 1. Introduction *nvim-api-intro* Nvim defines a C API as the primary way for external code to interact with -the NVim core. In the present version of Nvim the API is primarily used by +the Nvim core. In the present version of Nvim the API is primarily used by external processes to interact with Nvim using the msgpack-rpc protocol, see |msgpack-rpc|. The API will also be used from vimscript to access new Nvim core features, but this is not implemented yet. Later on, Nvim might be embeddable @@ -54,8 +54,8 @@ functions calling signature of the API functions types The custom handle types defined by Nvim error_types The possible kinds of errors an API function can exit with. -This metadata is mostly useful for external programs accessing the api over -msgpack-api, see |msgpack-rpc-api|. +This metadata is mostly useful for external programs accessing the API via +RPC, see |rpc-api|. ============================================================================== 4. Buffer highlighting *nvim-api-highlights* -- cgit