aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Genco <alexgenco@gmail.com>2014-11-13 21:47:08 -0800
committerAlex Genco <alexgenco@gmail.com>2014-11-13 21:47:08 -0800
commit92aba9e942909a4373674a12915db1d29b223443 (patch)
tree19e6ca0b3671c292372d83c84328e6f550a08efb
parentc7a3109dd3e747438f46ce6cc404006e27be79ff (diff)
downloadrneovim-92aba9e942909a4373674a12915db1d29b223443.tar.gz
rneovim-92aba9e942909a4373674a12915db1d29b223443.tar.bz2
rneovim-92aba9e942909a4373674a12915db1d29b223443.zip
Fix api metadata function name in docs
The documentation mentions `vim_get_api_metadata`, but the actual function is `vim_get_api_info`
-rw-r--r--runtime/doc/msgpack_rpc.txt4
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": {