aboutsummaryrefslogtreecommitdiff
path: root/runtime
diff options
context:
space:
mode:
authorJustin M. Keyes <justinkz@gmail.com>2016-12-11 02:04:33 +0100
committerGitHub <noreply@github.com>2016-12-11 02:04:33 +0100
commit29e651515fec1a4bc2cd41ed1c04eb5d03250525 (patch)
tree1ee201e49b49d9d2b9440fa92e5bdfb9b53dff04 /runtime
parent0fe89fc9d777d4b07684c33eb07b304e1e8285e3 (diff)
parente427cdf2d4799971cf45b36ea7344f37f115d02b (diff)
downloadrneovim-29e651515fec1a4bc2cd41ed1c04eb5d03250525.tar.gz
rneovim-29e651515fec1a4bc2cd41ed1c04eb5d03250525.tar.bz2
rneovim-29e651515fec1a4bc2cd41ed1c04eb5d03250525.zip
Merge #5752 from justinmk/doc
doc: api_info(), typval_encode.h
Diffstat (limited to 'runtime')
-rw-r--r--runtime/doc/api.txt23
1 files changed, 14 insertions, 9 deletions
diff --git a/runtime/doc/api.txt b/runtime/doc/api.txt
index 976b852bdb..171b0124f6 100644
--- a/runtime/doc/api.txt
+++ b/runtime/doc/api.txt
@@ -49,15 +49,20 @@ Tabpage -> enum value kObjectTypeTabpage
==============================================================================
3. API metadata *api-metadata*
-Nvim exposes metadata about the API as a Dictionary with the following keys:
-
-version Nvim version, API level/compatibility
-functions API function signatures
-types Custom handle types defined by Nvim
-error_types Possible error types returned by API functions
-
-This metadata is mostly useful for external programs accessing the API via
-RPC, see |rpc-api|.
+Nvim exposes API metadata as a Dictionary. Some items are described below:
+
+version Nvim version, API level/compatibility
+version.api_level Current API level
+version.api_compatible API is backwards-compatible with this level
+version.api_prerelease Declares the current API level as unstable >
+ (version.api_prerelease && fn.since == version.api_level)
+functions API function signatures
+{fn}.since API level where function {fn} was introduced
+{fn}.deprecated_since API level where function {fn} was deprecated
+types Custom handle types defined by Nvim
+error_types Possible error types returned by API functions
+
+External programs ("clients") can use the metadata to discover the |rpc-api|.
==============================================================================
4. Buffer highlighting *api-highlights*