diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2016-06-13 02:11:12 -0400 |
|---|---|---|
| committer | Justin M. Keyes <justinkz@gmail.com> | 2016-06-15 19:29:26 -0400 |
| commit | 23a3e58f02e37ed5c6f8fa1f4758d0ebe1aed8d3 (patch) | |
| tree | 4afeb551e0a0a2886b82f9682ddd40fbc9254e95 /runtime/doc/remote_plugin.txt | |
| parent | bd20892bdf15e45c4ea5827250e3aa0c2ace24a0 (diff) | |
| download | rneovim-23a3e58f02e37ed5c6f8fa1f4758d0ebe1aed8d3.tar.gz rneovim-23a3e58f02e37ed5c6f8fa1f4758d0ebe1aed8d3.tar.bz2 rneovim-23a3e58f02e37ed5c6f8fa1f4758d0ebe1aed8d3.zip | |
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.
Diffstat (limited to 'runtime/doc/remote_plugin.txt')
| -rw-r--r-- | runtime/doc/remote_plugin.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/runtime/doc/remote_plugin.txt b/runtime/doc/remote_plugin.txt index 139fcd83b9..3a2215f11c 100644 --- a/runtime/doc/remote_plugin.txt +++ b/runtime/doc/remote_plugin.txt @@ -16,8 +16,8 @@ Nvim support for remote plugins *remote-plugin* Extensibility is a primary goal of Nvim. Any programming language may be used to extend Nvim without changes to Nvim itself. This is achieved with remote -plugins, coprocesses that have a direct communication channel (via -|msgpack-rpc|) with the Nvim process. +plugins, coprocesses that have a direct communication channel (via |rpc|) with +the Nvim process. Even though these plugins run in separate processes they can call, be called, and receive events just as if the plugin's code were executed in the main @@ -33,9 +33,9 @@ check whether a plugin host is available for their chosen programming language. Plugin hosts are programs that provide a high-level environment for plugins, taking care of most boilerplate involved in defining commands, autocmds, and -functions that are implemented over |msgpack-rpc| connections. Hosts are -loaded only when one of their registered plugins require it, keeping Nvim's -startup as fast as possible, even if many plugins/hosts are installed. +functions that are implemented over |rpc| connections. Hosts are loaded only +when one of their registered plugins require it, keeping Nvim's startup as +fast as possible, even if many plugins/hosts are installed. ============================================================================== 3. Example *remote-plugin-example* |