From 92aba9e942909a4373674a12915db1d29b223443 Mon Sep 17 00:00:00 2001 From: Alex Genco Date: Thu, 13 Nov 2014 21:47:08 -0800 Subject: [PATCH] Fix api metadata function name in docs The documentation mentions `vim_get_api_metadata`, but the actual function is `vim_get_api_info` --- runtime/doc/msgpack_rpc.txt | 4 ++-- 1 file 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": {