diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2014-11-14 10:59:18 -0500 |
|---|---|---|
| committer | Justin M. Keyes <justinkz@gmail.com> | 2014-11-14 10:59:18 -0500 |
| commit | c347d9226a00d1ff8015fcdab1fb414e2c3e4c0a (patch) | |
| tree | 19e6ca0b3671c292372d83c84328e6f550a08efb | |
| parent | c7a3109dd3e747438f46ce6cc404006e27be79ff (diff) | |
| parent | 92aba9e942909a4373674a12915db1d29b223443 (diff) | |
| download | rneovim-c347d9226a00d1ff8015fcdab1fb414e2c3e4c0a.tar.gz rneovim-c347d9226a00d1ff8015fcdab1fb414e2c3e4c0a.tar.bz2 rneovim-c347d9226a00d1ff8015fcdab1fb414e2c3e4c0a.zip | |
Merge pull request #1473 from alexgenco/patch-1
Fix api metadata function name in docs
| -rw-r--r-- | runtime/doc/msgpack_rpc.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/doc/msgpack_rpc.txt b/runtime/doc/msgpack_rpc.txt index 800ab08ce3..3d8ae276ce 100644 --- a/runtime/doc/msgpack_rpc.txt +++ b/runtime/doc/msgpack_rpc.txt @@ -50,7 +50,7 @@ metadata from a compiled nvim instance. There are two ways to obtain API metadata: -1. By connecting to a running nvim instance and calling `vim_get_api_metadata` +1. By connecting to a running nvim instance and calling `vim_get_api_info` via msgpack-rpc. This is the preferred way for clients written in dynamically-typed languages, which can define functions at runtime. @@ -179,7 +179,7 @@ Tabpage -> enum value kObjectTypeTabpage The most reliable way of determining the type codes for the special nvim types is at runtime by inspecting the `types` key of metadata dictionary returned by -`vim_get_api_metadata` method. Here's an example json representation of the +`vim_get_api_info` method. Here's an example json representation of the `types` object: > "types": { |