IntenseFinance/neovim
3
0
Fork 0
mirror of https://github.com/neovim/neovim.git synced 2025-02-25 18:55:25 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1473 from alexgenco/patch-1

Browse Source 
Fix api metadata function name in docs
This commit is contained in:
Justin M. Keyes 2014-11-14 10:59:18 -05:00
commit c347d9226a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
runtime/doc/msgpack_rpc.txt
View File

@ -50,7 +50,7 @@ metadata from a compiled nvim instance.
There are two ways to obtain API metadata: 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 via msgpack-rpc. This is the preferred way for clients written in
dynamically-typed languages, which can define functions at runtime. 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 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 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` object:
> >
"types": { "types": {