2017-03-21 09:08:19 -07:00
|
|
|
*api.txt* Nvim
|
2016-02-07 05:05:59 -07:00
|
|
|
|
|
|
|
|
|
|
|
NVIM REFERENCE MANUAL by Thiago de Arruda
|
|
|
|
|
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
Nvim API *API* *api*
|
2016-06-14 20:12:43 -07:00
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
Nvim exposes a powerful API that can be used by plugins and external processes
|
2017-08-19 05:13:14 -07:00
|
|
|
via |RPC|, |Lua| and VimL (|eval-api|).
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2017-04-17 14:52:38 -07:00
|
|
|
Applications can also embed libnvim to work with the C API directly.
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2017-10-20 17:33:58 -07:00
|
|
|
Type |gO| to see the table of contents.
|
2017-05-01 08:09:29 -07:00
|
|
|
|
2019-08-25 16:00:58 -07:00
|
|
|
==============================================================================
|
|
|
|
API Usage *api-rpc* *RPC* *rpc*
|
|
|
|
|
|
|
|
*msgpack-rpc*
|
|
|
|
RPC is the typical way to control Nvim programmatically. Nvim implements the
|
|
|
|
MessagePack-RPC protocol:
|
2019-11-25 02:08:02 -07:00
|
|
|
https://github.com/msgpack-rpc/msgpack-rpc/blob/master/spec.md
|
2019-08-25 16:00:58 -07:00
|
|
|
https://github.com/msgpack/msgpack/blob/0b8f5ac/spec.md
|
|
|
|
|
|
|
|
Many clients use the API: user interfaces (GUIs), remote plugins, scripts like
|
|
|
|
"nvr" (https://github.com/mhinz/neovim-remote). Even Nvim itself can control
|
|
|
|
other Nvim instances. API clients can:
|
|
|
|
|
|
|
|
- Call any API function
|
|
|
|
- Listen for events
|
|
|
|
- Receive remote calls from Nvim
|
|
|
|
|
|
|
|
The RPC API is like a more powerful version of Vim's "clientserver" feature.
|
|
|
|
|
|
|
|
CONNECTING *rpc-connecting*
|
|
|
|
|
|
|
|
See |channel-intro| for various ways to open a channel. Channel-opening
|
|
|
|
functions take an `rpc` key in the options dictionary. RPC channels can also
|
|
|
|
be opened by other processes connecting to TCP/IP sockets or named pipes
|
|
|
|
listened to by Nvim.
|
|
|
|
|
|
|
|
Nvim creates a default RPC socket at |startup|, given by |v:servername|. To
|
|
|
|
start with a TCP/IP socket instead, use |--listen| with a TCP-style address: >
|
|
|
|
nvim --listen 127.0.0.1:6666
|
|
|
|
More endpoints can be started with |serverstart()|.
|
|
|
|
|
|
|
|
Note that localhost TCP sockets are generally less secure than named pipes,
|
|
|
|
and can lead to vunerabilities like remote code execution.
|
|
|
|
|
|
|
|
Connecting to the socket is the easiest way a programmer can test the API,
|
|
|
|
which can be done through any msgpack-rpc client library or full-featured
|
|
|
|
|api-client|. Here's a Ruby script that prints "hello world!" in the current
|
|
|
|
Nvim instance:
|
|
|
|
>
|
|
|
|
#!/usr/bin/env ruby
|
|
|
|
# Requires msgpack-rpc: gem install msgpack-rpc
|
|
|
|
#
|
|
|
|
# To run this script, execute it from a running Nvim instance (notice the
|
|
|
|
# trailing '&' which is required since Nvim won't process events while
|
|
|
|
# running a blocking command):
|
|
|
|
#
|
|
|
|
# :!./hello.rb &
|
|
|
|
#
|
|
|
|
# Or from another shell by setting NVIM_LISTEN_ADDRESS:
|
|
|
|
# $ NVIM_LISTEN_ADDRESS=[address] ./hello.rb
|
|
|
|
|
|
|
|
require 'msgpack/rpc'
|
|
|
|
require 'msgpack/rpc/transport/unix'
|
|
|
|
|
|
|
|
nvim = MessagePack::RPC::Client.new(MessagePack::RPC::UNIXTransport.new, ENV['NVIM_LISTEN_ADDRESS'])
|
|
|
|
result = nvim.call(:nvim_command, 'echo "hello world!"')
|
|
|
|
<
|
2020-08-31 00:51:35 -07:00
|
|
|
A better way is to use the Python REPL with the "pynvim" package, where API
|
2019-08-25 16:00:58 -07:00
|
|
|
functions can be called interactively:
|
|
|
|
>
|
|
|
|
>>> from pynvim import attach
|
|
|
|
>>> nvim = attach('socket', path='[address]')
|
|
|
|
>>> nvim.command('echo "hello world!"')
|
|
|
|
<
|
|
|
|
You can also embed Nvim via |jobstart()|, and communicate using |rpcrequest()|
|
|
|
|
and |rpcnotify()|:
|
|
|
|
>
|
|
|
|
let nvim = jobstart(['nvim', '--embed'], {'rpc': v:true})
|
|
|
|
echo rpcrequest(nvim, 'nvim_eval', '"Hello " . "world!"')
|
|
|
|
call jobstop(nvim)
|
|
|
|
|
2016-02-07 05:05:59 -07:00
|
|
|
==============================================================================
|
2019-05-24 09:07:16 -07:00
|
|
|
API Definitions *api-definitions*
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2019-05-24 09:07:16 -07:00
|
|
|
*api-types*
|
2017-12-27 11:30:23 -07:00
|
|
|
The Nvim C API defines custom types for all function parameters. Some are just
|
|
|
|
typedefs around C99 standard types, others are Nvim-defined data structures.
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2019-08-25 16:00:58 -07:00
|
|
|
Basic types ~
|
|
|
|
|
|
|
|
API Type C type
|
|
|
|
------------------------------------------------------------------------
|
|
|
|
Nil
|
|
|
|
Boolean bool
|
|
|
|
Integer (signed 64-bit integer) int64_t
|
|
|
|
Float (IEEE 754 double precision) double
|
|
|
|
String {char* data, size_t size} struct
|
2017-12-27 11:30:23 -07:00
|
|
|
Array
|
2019-08-25 16:00:58 -07:00
|
|
|
Dictionary (msgpack: map)
|
2017-12-27 11:30:23 -07:00
|
|
|
Object
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2019-08-25 16:00:58 -07:00
|
|
|
Note: empty Array is accepted as a valid argument for Dictionary parameter.
|
|
|
|
|
|
|
|
Special types (msgpack EXT) ~
|
|
|
|
|
|
|
|
These are integer typedefs discriminated as separate Object subtypes. They
|
|
|
|
can be treated as opaque integers, but are mutually incompatible: Buffer may
|
|
|
|
be passed as an integer but not as Window or Tabpage.
|
|
|
|
|
|
|
|
The EXT object data is the (integer) object handle. The EXT type codes given
|
|
|
|
in the |api-metadata| `types` key are stable: they will not change and are
|
|
|
|
thus forward-compatible.
|
|
|
|
|
|
|
|
EXT Type C type Data
|
|
|
|
------------------------------------------------------------------------
|
|
|
|
Buffer enum value kObjectTypeBuffer |bufnr()|
|
|
|
|
Window enum value kObjectTypeWindow |window-ID|
|
|
|
|
Tabpage enum value kObjectTypeTabpage internal handle
|
2016-02-07 05:05:59 -07:00
|
|
|
|
|
|
|
|
2019-05-24 09:07:16 -07:00
|
|
|
*api-indexing*
|
|
|
|
Most of the API uses 0-based indices, and ranges are end-exclusive. For the
|
|
|
|
end of a range, -1 denotes the last line/column.
|
|
|
|
|
|
|
|
Exception: the following API functions use "mark-like" indexing (1-based
|
|
|
|
lines, 0-based columns):
|
|
|
|
|
|
|
|
|nvim_buf_get_mark()|
|
|
|
|
|nvim_win_get_cursor()|
|
|
|
|
|nvim_win_set_cursor()|
|
|
|
|
|
2019-08-25 16:01:01 -07:00
|
|
|
*api-fast*
|
|
|
|
Most API functions are "deferred": they are queued on the main loop and
|
|
|
|
processed sequentially with normal input. So if the editor is waiting for
|
|
|
|
user input in a "modal" fashion (e.g. the |hit-enter-prompt|), the request
|
|
|
|
will block. Non-deferred ({fast}) functions such as |nvim_get_mode()| and
|
|
|
|
|nvim_input()| are served immediately (i.e. without waiting in the input
|
|
|
|
queue). Lua code can use |vim.in_fast_event()| to detect a {fast} context.
|
|
|
|
|
2016-02-07 05:05:59 -07:00
|
|
|
==============================================================================
|
2019-08-25 16:00:58 -07:00
|
|
|
API metadata *api-metadata*
|
|
|
|
|
|
|
|
The Nvim C API is automatically exposed to RPC by the build system, which
|
|
|
|
parses headers in src/nvim/api/* and generates dispatch-functions mapping RPC
|
|
|
|
API method names to public C API functions, converting/validating arguments
|
|
|
|
and return values.
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2019-08-25 16:00:58 -07:00
|
|
|
Nvim exposes its API metadata as a Dictionary with these items:
|
2016-10-31 08:16:37 -07:00
|
|
|
|
|
|
|
version Nvim version, API level/compatibility
|
2019-01-27 07:06:11 -07:00
|
|
|
version.api_level API version integer *api-level*
|
2016-10-31 08:16:37 -07:00
|
|
|
version.api_compatible API is backwards-compatible with this level
|
2019-01-27 07:06:11 -07:00
|
|
|
version.api_prerelease Declares the API as unstable/unreleased >
|
2016-10-31 08:16:37 -07:00
|
|
|
(version.api_prerelease && fn.since == version.api_level)
|
2019-08-25 16:00:58 -07:00
|
|
|
functions API function signatures, containing |api-types| info
|
|
|
|
describing the return value and parameters.
|
|
|
|
ui_events |UI| event signatures
|
2019-05-11 07:58:47 -07:00
|
|
|
ui_options Supported |ui-option|s
|
2016-10-31 08:16:37 -07:00
|
|
|
{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
|
|
|
|
|
2019-08-25 16:00:58 -07:00
|
|
|
About the `functions` map:
|
|
|
|
|
|
|
|
- Container types may be decorated with type/size constraints, e.g.
|
|
|
|
ArrayOf(Buffer) or ArrayOf(Integer, 2).
|
|
|
|
- Functions considered to be methods that operate on instances of Nvim
|
|
|
|
special types (msgpack EXT) have the "method=true" flag. The receiver type
|
|
|
|
is that of the first argument. Method names are prefixed with `nvim_` plus
|
|
|
|
a type name, e.g. `nvim_buf_get_lines` is the `get_lines` method of
|
|
|
|
a Buffer instance. |dev-api|
|
|
|
|
- Global functions have the "method=false" flag and are prefixed with just
|
|
|
|
`nvim_`, e.g. `nvim_get_buffers`.
|
|
|
|
|
|
|
|
*api-mapping*
|
|
|
|
External programs (clients) can use the metadata to discover the API, using
|
|
|
|
any of these approaches:
|
|
|
|
|
|
|
|
1. Connect to a running Nvim instance and call |nvim_get_api_info()| via
|
2020-01-13 00:41:55 -07:00
|
|
|
msgpack-RPC. This is best for clients written in dynamic languages which
|
2019-08-25 16:00:58 -07:00
|
|
|
can define functions at runtime.
|
|
|
|
|
2020-01-13 00:41:55 -07:00
|
|
|
2. Start Nvim with |--api-info|. Useful for statically-compiled clients.
|
|
|
|
Example (requires Python "pyyaml" and "msgpack-python" modules): >
|
|
|
|
nvim --api-info | python -c 'import msgpack, sys, yaml; print yaml.dump(msgpack.unpackb(sys.stdin.read()))'
|
2019-08-25 16:00:58 -07:00
|
|
|
<
|
2020-01-13 00:41:55 -07:00
|
|
|
3. Use the |api_info()| Vimscript function. >
|
|
|
|
:lua print(vim.inspect(vim.fn.api_info()))
|
|
|
|
< Example using |filter()| to exclude non-deprecated API functions: >
|
|
|
|
:new|put =map(filter(api_info().functions, '!has_key(v:val,''deprecated_since'')'), 'v:val.name')
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2017-04-17 14:52:38 -07:00
|
|
|
==============================================================================
|
|
|
|
API contract *api-contract*
|
|
|
|
|
2017-12-27 11:30:23 -07:00
|
|
|
The Nvim API is composed of functions and events.
|
|
|
|
|
|
|
|
- Clients call functions like those described at |api-global|.
|
|
|
|
- Clients can subscribe to |ui-events|, |api-buffer-updates|, etc.
|
|
|
|
- API function names are prefixed with "nvim_".
|
|
|
|
- API event names are prefixed with "nvim_" and suffixed with "_event".
|
2017-04-17 14:52:38 -07:00
|
|
|
|
2017-12-27 11:30:23 -07:00
|
|
|
As Nvim evolves the API may change in compliance with this CONTRACT:
|
2017-04-17 14:52:38 -07:00
|
|
|
|
|
|
|
- New functions and events may be added.
|
|
|
|
- Any such extensions are OPTIONAL: old clients may ignore them.
|
|
|
|
- Function signatures will NOT CHANGE (after release).
|
|
|
|
- Functions introduced in the development (unreleased) version MAY CHANGE.
|
|
|
|
(Clients can dynamically check `api_prerelease`, etc. |api-metadata|)
|
|
|
|
- Event parameters will not be removed or reordered (after release).
|
|
|
|
- Events may be EXTENDED: new parameters may be added.
|
|
|
|
- New items may be ADDED to map/list parameters/results of functions and
|
|
|
|
events.
|
|
|
|
- Any such new items are OPTIONAL: old clients may ignore them.
|
|
|
|
- Existing items will not be removed (after release).
|
|
|
|
- Deprecated functions will not be removed until Nvim version 2.0
|
|
|
|
|
2018-12-01 08:44:36 -07:00
|
|
|
==============================================================================
|
|
|
|
Global events *api-global-events*
|
|
|
|
|
|
|
|
When a client invokes an API request as an async notification, it is not
|
|
|
|
possible for Nvim to send an error response. Instead, in case of error, the
|
|
|
|
following notification will be sent to the client:
|
|
|
|
|
|
|
|
*nvim_error_event*
|
|
|
|
nvim_error_event[{type}, {message}]
|
|
|
|
|
|
|
|
{type} is a numeric id as defined by `api_info().error_types`, and {message} is
|
|
|
|
a string with the error message.
|
|
|
|
|
2016-02-07 05:05:59 -07:00
|
|
|
==============================================================================
|
2018-06-08 01:19:46 -07:00
|
|
|
Buffer update events *api-buffer-updates*
|
|
|
|
|
|
|
|
API clients can "attach" to Nvim buffers to subscribe to buffer update events.
|
|
|
|
This is similar to |TextChanged| but more powerful and granular.
|
|
|
|
|
2018-08-25 07:38:24 -07:00
|
|
|
Call |nvim_buf_attach()| to receive these events on the channel:
|
2018-06-08 01:19:46 -07:00
|
|
|
|
|
|
|
*nvim_buf_lines_event*
|
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, {firstline}, {lastline}, {linedata}, {more}]
|
|
|
|
|
|
|
|
When the buffer text between {firstline} and {lastline} (end-exclusive,
|
|
|
|
zero-indexed) were changed to the new text in the {linedata} list. The
|
|
|
|
granularity is a line, i.e. if a single character is changed in the editor,
|
|
|
|
the entire line is sent.
|
|
|
|
|
|
|
|
When {changedtick} is |v:null| this means the screen lines (display) changed
|
|
|
|
but not the buffer contents. {linedata} contains the changed screen lines.
|
2018-11-04 18:47:22 -07:00
|
|
|
This happens when 'inccommand' shows a buffer preview.
|
2018-06-08 01:19:46 -07:00
|
|
|
|
|
|
|
Properties:~
|
|
|
|
{buf} API buffer handle (buffer number)
|
|
|
|
|
|
|
|
{changedtick} value of |b:changedtick| for the buffer. If you send an API
|
|
|
|
command back to nvim you can check the value of |b:changedtick| as part of
|
|
|
|
your request to ensure that no other changes have been made.
|
|
|
|
|
|
|
|
{firstline} integer line number of the first line that was replaced.
|
|
|
|
Zero-indexed: if line 1 was replaced then {firstline} will be 0, not 1.
|
|
|
|
{firstline} is always less than or equal to the number of lines that were
|
|
|
|
in the buffer before the lines were replaced.
|
|
|
|
|
|
|
|
{lastline} integer line number of the first line that was not replaced
|
|
|
|
(i.e. the range {firstline}, {lastline} is end-exclusive).
|
|
|
|
Zero-indexed: if line numbers 2 to 5 were replaced, this will be 5 instead
|
|
|
|
of 6. {lastline} is always be less than or equal to the number of lines
|
|
|
|
that were in the buffer before the lines were replaced. {lastline} will be
|
|
|
|
-1 if the event is part of the initial update after attaching.
|
|
|
|
|
|
|
|
{linedata} list of strings containing the contents of the new buffer
|
|
|
|
lines. Newline characters are omitted; empty lines are sent as empty
|
|
|
|
strings.
|
|
|
|
|
|
|
|
{more} boolean, true for a "multipart" change notification: the current
|
|
|
|
change was chunked into multiple |nvim_buf_lines_event| notifications
|
|
|
|
(e.g. because it was too big).
|
|
|
|
|
|
|
|
nvim_buf_changedtick_event[{buf}, {changedtick}] *nvim_buf_changedtick_event*
|
|
|
|
|
|
|
|
When |b:changedtick| was incremented but no text was changed. Relevant for
|
|
|
|
undo/redo.
|
|
|
|
|
|
|
|
Properties:~
|
|
|
|
{buf} API buffer handle (buffer number)
|
|
|
|
{changedtick} new value of |b:changedtick| for the buffer
|
|
|
|
|
|
|
|
nvim_buf_detach_event[{buf}] *nvim_buf_detach_event*
|
|
|
|
|
|
|
|
When buffer is detached (i.e. updates are disabled). Triggered explicitly by
|
2018-11-04 18:47:22 -07:00
|
|
|
|nvim_buf_detach()| or implicitly in these cases:
|
2018-06-08 01:19:46 -07:00
|
|
|
- Buffer was |abandon|ed and 'hidden' is not set.
|
|
|
|
- Buffer was reloaded, e.g. with |:edit| or an external change triggered
|
|
|
|
|:checktime| or 'autoread'.
|
|
|
|
- Generally: whenever the buffer contents are unloaded from memory.
|
|
|
|
|
|
|
|
Properties:~
|
|
|
|
{buf} API buffer handle (buffer number)
|
|
|
|
|
|
|
|
|
|
|
|
EXAMPLE ~
|
|
|
|
|
2018-08-25 07:38:24 -07:00
|
|
|
Calling |nvim_buf_attach()| with send_buffer=true on an empty buffer, emits: >
|
2019-01-21 20:43:44 -07:00
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, 0, -1, [""], v:false]
|
2018-06-08 01:19:46 -07:00
|
|
|
|
|
|
|
User adds two lines to the buffer, emits: >
|
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, 0, 0, ["line1", "line2"], v:false]
|
|
|
|
|
|
|
|
User moves to a line containing the text "Hello world" and inserts "!", emits: >
|
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, {linenr}, {linenr} + 1,
|
|
|
|
["Hello world!"], v:false]
|
|
|
|
|
|
|
|
User moves to line 3 and deletes 20 lines using "20dd", emits: >
|
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, 2, 22, [], v:false]
|
|
|
|
|
|
|
|
User selects lines 3-5 using |linewise-visual| mode and then types "p" to
|
|
|
|
paste a block of 6 lines, emits: >
|
|
|
|
nvim_buf_lines_event[{buf}, {changedtick}, 2, 5,
|
|
|
|
['pasted line 1', 'pasted line 2', 'pasted line 3', 'pasted line 4',
|
|
|
|
'pasted line 5', 'pasted line 6'],
|
|
|
|
v:false
|
|
|
|
]
|
|
|
|
|
|
|
|
User reloads the buffer with ":edit", emits: >
|
|
|
|
nvim_buf_detach_event[{buf}]
|
2019-08-28 01:17:45 -07:00
|
|
|
<
|
2018-06-08 01:19:46 -07:00
|
|
|
|
2019-08-28 01:17:45 -07:00
|
|
|
LUA ~
|
2019-05-29 01:05:00 -07:00
|
|
|
*api-buffer-updates-lua*
|
2019-08-28 01:17:45 -07:00
|
|
|
In-process Lua plugins can receive buffer updates in the form of Lua
|
|
|
|
callbacks. These callbacks are called frequently in various contexts;
|
|
|
|
|textlock| prevents changing buffer contents and window layout (use
|
|
|
|
|vim.schedule| to defer such operations to the main loop instead).
|
2019-05-29 01:05:00 -07:00
|
|
|
|
2020-09-05 22:10:56 -07:00
|
|
|
|nvim_buf_attach()| will take keyword args for the callbacks. "on_lines" will
|
2019-07-15 09:23:11 -07:00
|
|
|
receive parameters ("lines", {buf}, {changedtick}, {firstline}, {lastline},
|
2019-08-04 03:22:22 -07:00
|
|
|
{new_lastline}, {old_byte_size}[, {old_utf32_size}, {old_utf16_size}]).
|
2019-07-15 09:23:11 -07:00
|
|
|
Unlike remote channel events the text contents are not passed. The new text can
|
|
|
|
be accessed inside the callback as
|
|
|
|
|
|
|
|
`vim.api.nvim_buf_get_lines(buf, firstline, new_lastline, true)`
|
|
|
|
|
2019-08-04 03:22:22 -07:00
|
|
|
{old_byte_size} is the total size of the replaced region {firstline} to
|
|
|
|
{lastline} in bytes, including the final newline after {lastline}. if
|
|
|
|
`utf_sizes` is set to true in |nvim_buf_attach()| keyword args, then the
|
|
|
|
UTF-32 and UTF-16 sizes of the deleted region is also passed as additional
|
|
|
|
arguments {old_utf32_size} and {old_utf16_size}.
|
2019-07-15 09:23:11 -07:00
|
|
|
|
2019-05-29 01:05:00 -07:00
|
|
|
"on_changedtick" is invoked when |b:changedtick| was incremented but no text
|
|
|
|
was changed. The parameters recieved are ("changedtick", {buf}, {changedtick}).
|
|
|
|
|
2019-08-28 01:17:45 -07:00
|
|
|
*api-lua-detach*
|
|
|
|
In-process Lua callbacks can detach by returning `true`. This will detach all
|
2020-09-05 22:10:56 -07:00
|
|
|
callbacks attached with the same |nvim_buf_attach()| call.
|
2019-05-29 01:05:00 -07:00
|
|
|
|
|
|
|
|
2018-06-08 01:19:46 -07:00
|
|
|
==============================================================================
|
2017-03-01 09:18:03 -07:00
|
|
|
Buffer highlighting *api-highlights*
|
2016-02-07 05:05:59 -07:00
|
|
|
|
|
|
|
Nvim allows plugins to add position-based highlights to buffers. This is
|
|
|
|
similar to |matchaddpos()| but with some key differences. The added highlights
|
|
|
|
are associated with a buffer and adapts to line insertions and deletions,
|
|
|
|
similar to signs. It is also possible to manage a set of highlights as a group
|
|
|
|
and delete or replace all at once.
|
|
|
|
|
|
|
|
The intended use case are linter or semantic highlighter plugins that monitor
|
|
|
|
a buffer for changes, and in the background compute highlights to the buffer.
|
|
|
|
Another use case are plugins that show output in an append-only buffer, and
|
|
|
|
want to add highlights to the outputs. Highlight data cannot be preserved
|
|
|
|
on writing and loading a buffer to file, nor in undo/redo cycles.
|
|
|
|
|
2018-08-25 07:38:24 -07:00
|
|
|
Highlights are registered using the |nvim_buf_add_highlight()| function. If an
|
|
|
|
external highlighter plugin wants to add many highlights in a batch,
|
|
|
|
performance can be improved by calling |nvim_buf_add_highlight()| as an
|
2020-12-26 21:49:21 -07:00
|
|
|
asynchronous notification, after first (synchronously) requesting a source id.
|
2019-04-08 14:08:01 -07:00
|
|
|
|
|
|
|
Example using the Python API client (|pynvim|):
|
2016-02-07 05:05:59 -07:00
|
|
|
>
|
|
|
|
src = vim.new_highlight_source()
|
|
|
|
buf = vim.current.buffer
|
|
|
|
for i in range(5):
|
|
|
|
buf.add_highlight("String",i,0,-1,src_id=src)
|
2019-04-08 14:08:01 -07:00
|
|
|
# some time later ...
|
|
|
|
buf.clear_namespace(src)
|
2016-02-07 05:05:59 -07:00
|
|
|
<
|
|
|
|
If the highlights don't need to be deleted or updated, just pass -1 as
|
2018-12-01 08:44:36 -07:00
|
|
|
src_id (this is the default in python). Use |nvim_buf_clear_namespace()| to
|
2018-08-25 07:38:24 -07:00
|
|
|
clear highlights from a specific source, in a specific line range or the
|
|
|
|
entire buffer by passing in the line range 0, -1 (the latter is the default in
|
|
|
|
python as used above).
|
2016-02-07 05:05:59 -07:00
|
|
|
|
2019-04-08 14:08:01 -07:00
|
|
|
Example using the API from Vimscript: >
|
2016-06-28 12:45:19 -07:00
|
|
|
|
|
|
|
call nvim_buf_set_lines(0, 0, 0, v:true, ["test text"])
|
|
|
|
let src = nvim_buf_add_highlight(0, 0, "String", 1, 0, 4)
|
|
|
|
call nvim_buf_add_highlight(0, src, "Identifier", 0, 5, -1)
|
2019-04-08 14:08:01 -07:00
|
|
|
" some time later ...
|
2018-12-01 08:44:36 -07:00
|
|
|
call nvim_buf_clear_namespace(0, src, 0, -1)
|
2019-03-03 04:38:14 -07:00
|
|
|
|
|
|
|
|
|
|
|
==============================================================================
|
|
|
|
Floating windows *api-floatwin*
|
|
|
|
|
2019-09-09 15:35:30 -07:00
|
|
|
Floating windows ("floats") are displayed on top of normal windows. This is
|
|
|
|
useful to implement simple widgets, such as tooltips displayed next to the
|
|
|
|
cursor. Floats are fully functional windows supporting user editing, common
|
|
|
|
|api-window| calls, and most window options (except 'statusline').
|
|
|
|
|
|
|
|
Two ways to create a floating window:
|
|
|
|
- |nvim_open_win()| creates a new window (needs a buffer, see |nvim_create_buf()|)
|
|
|
|
- |nvim_win_set_config()| reconfigures a normal window into a float
|
|
|
|
|
|
|
|
To close it use |nvim_win_close()| or a command such as |:close|.
|
|
|
|
|
|
|
|
Buffer text can be highlighted by typical mechanisms (syntax highlighting,
|
|
|
|
|api-highlights|). The |hl-NormalFloat| group highlights normal text;
|
|
|
|
'winhighlight' can be used as usual to override groups locally. Floats inherit
|
|
|
|
options from the current window; specify `style=minimal` in |nvim_open_win()|
|
|
|
|
to disable various visual features such as the 'number' column.
|
|
|
|
|
|
|
|
Currently, floating windows don't support widgets like border or scrollbar.
|
|
|
|
|
|
|
|
Example: create a float with scratch buffer: >
|
2019-03-03 04:38:14 -07:00
|
|
|
|
|
|
|
let buf = nvim_create_buf(v:false, v:true)
|
|
|
|
call nvim_buf_set_lines(buf, 0, -1, v:true, ["test", "text"])
|
2019-03-15 10:18:56 -07:00
|
|
|
let opts = {'relative': 'cursor', 'width': 10, 'height': 2, 'col': 0,
|
2019-05-30 08:46:41 -07:00
|
|
|
\ 'row': 1, 'anchor': 'NW', 'style': 'minimal'}
|
2019-03-15 10:18:56 -07:00
|
|
|
let win = nvim_open_win(buf, 0, opts)
|
2019-03-03 04:38:14 -07:00
|
|
|
" optional: change highlight, otherwise Pmenu is used
|
|
|
|
call nvim_win_set_option(win, 'winhl', 'Normal:MyHighlight')
|
2016-06-28 12:45:19 -07:00
|
|
|
>
|
2019-08-25 16:00:52 -07:00
|
|
|
|
2017-01-18 05:20:07 -07:00
|
|
|
==============================================================================
|
2019-11-09 04:41:50 -07:00
|
|
|
Extended marks *api-extended-marks*
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
Extended marks (extmarks) represent buffer annotations that track text changes
|
|
|
|
in the buffer. They could be used to represent cursors, folds, misspelled
|
|
|
|
words, and anything else that needs to track a logical location in the buffer
|
|
|
|
over time.
|
2017-01-18 05:20:07 -07:00
|
|
|
|
|
|
|
Example:
|
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
We will set an extmark at the first row and third column. |api-indexing| is
|
|
|
|
zero-indexed, so we use row=0 and column=2. Passing id=0 creates a new mark
|
|
|
|
and returns the id: >
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
let g:mark_ns = nvim_create_namespace('myplugin')
|
|
|
|
let g:mark_id = nvim_buf_set_extmark(0, g:mark_ns, 0, 0, 2, {})
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
We can get a mark by its id: >
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
echo nvim_buf_get_extmark_by_id(0, g:mark_ns, g:mark_id)
|
|
|
|
=> [0, 2]
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
We can get all marks in a buffer for our namespace (or by a range): >
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-17 20:06:59 -07:00
|
|
|
echo nvim_buf_get_extmarks(0, g:mark_ns, 0, -1, {})
|
2019-11-10 17:52:14 -07:00
|
|
|
=> [[1, 0, 2]]
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
Deleting all text surrounding an extmark does not remove the extmark. To
|
|
|
|
remove an extmark use |nvim_buf_del_extmark()|.
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2019-11-10 17:52:14 -07:00
|
|
|
Namespaces allow your plugin to manage only its own extmarks, ignoring those
|
|
|
|
created by another plugin.
|
|
|
|
|
|
|
|
Extmark positions changed by an edit will be restored on undo/redo. Creating
|
|
|
|
and deleting extmarks is not a buffer change, thus new undo states are not
|
|
|
|
created for extmark changes.
|
2017-01-18 05:20:07 -07:00
|
|
|
|
2016-02-07 05:05:59 -07:00
|
|
|
==============================================================================
|
2017-03-01 09:18:03 -07:00
|
|
|
Global Functions *api-global*
|
|
|
|
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
nvim__get_hl_defs({ns_id}) *nvim__get_hl_defs()*
|
|
|
|
TODO: Documentation
|
|
|
|
|
2020-07-02 04:09:17 -07:00
|
|
|
nvim__get_lib_dir() *nvim__get_lib_dir()*
|
|
|
|
TODO: Documentation
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__id({obj}) *nvim__id()*
|
|
|
|
Returns object given as argument.
|
2019-12-01 23:43:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
This API function is used for testing. One should not rely on
|
|
|
|
its presence in plugins.
|
2019-12-01 23:43:16 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{obj} Object to return.
|
2019-12-01 23:43:16 -07:00
|
|
|
|
2019-12-02 01:46:46 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
its argument.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__id_array({arr}) *nvim__id_array()*
|
|
|
|
Returns array given as argument.
|
2019-12-01 23:43:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
This API function is used for testing. One should not rely on
|
|
|
|
its presence in plugins.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{arr} Array to return.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
its argument.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__id_dictionary({dct}) *nvim__id_dictionary()*
|
|
|
|
Returns dictionary given as argument.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
This API function is used for testing. One should not rely on
|
|
|
|
its presence in plugins.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{dct} Dictionary to return.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
its argument.
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__id_float({flt}) *nvim__id_float()*
|
|
|
|
Returns floating-point value given as argument.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
This API function is used for testing. One should not rely on
|
|
|
|
its presence in plugins.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{flt} Value to return.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
its argument.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__inspect_cell({grid}, {row}, {col}) *nvim__inspect_cell()*
|
|
|
|
TODO: Documentation
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2020-09-06 16:55:49 -07:00
|
|
|
nvim__screenshot({path}) *nvim__screenshot()*
|
|
|
|
TODO: Documentation
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
2021-03-15 01:58:39 -07:00
|
|
|
nvim__set_hl_ns({ns_id}) *nvim__set_hl_ns()*
|
|
|
|
Set active namespace for highlights.
|
|
|
|
|
|
|
|
NB: this function can be called from async contexts, but the
|
|
|
|
semantics are not yet well-defined. To start with
|
|
|
|
|nvim_set_decoration_provider| on_win and on_line callbacks
|
|
|
|
are explicitly allowed to change the namespace during a redraw
|
|
|
|
cycle.
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{ns_id} the namespace to activate
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim__stats() *nvim__stats()*
|
|
|
|
Gets internal stats.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Map of various internal stats.
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_call_atomic({calls}) *nvim_call_atomic()*
|
|
|
|
Calls many API methods atomically.
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
This has two main usages:
|
|
|
|
1. To perform several requests from an async context
|
|
|
|
atomically, i.e. without interleaving redraws, RPC requests
|
|
|
|
from other clients, or user interactions (however API
|
|
|
|
methods may trigger autocommands or event processing which
|
|
|
|
have such side-effects, e.g. |:sleep| may wake timers).
|
|
|
|
2. To minimize RPC overhead (roundtrips) of a sequence of many
|
|
|
|
requests.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{calls} an array of calls, where each call is described
|
|
|
|
by an array with two elements: the request name,
|
|
|
|
and an array of arguments.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Array of two elements. The first is an array of return
|
|
|
|
values. The second is NIL if all calls succeeded. If a
|
|
|
|
call resulted in an error, it is a three-element array
|
|
|
|
with the zero-based index of the call which resulted in an
|
|
|
|
error, the error type and the error message. If an error
|
|
|
|
occurred, the values from all preceding calls will still
|
|
|
|
be returned.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-31 07:52:14 -07:00
|
|
|
*nvim_call_dict_function()*
|
|
|
|
nvim_call_dict_function({dict}, {fn}, {args})
|
2019-12-28 04:27:25 -07:00
|
|
|
Calls a VimL |Dictionary-function| with the given arguments.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-10 15:20:39 -07:00
|
|
|
On execution error: fails with VimL error, does not update
|
|
|
|
v:errmsg.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{dict} Dictionary, or String evaluating to a VimL |self|
|
|
|
|
dict
|
|
|
|
{fn} Name of the function defined on the VimL dict
|
|
|
|
{args} Function arguments packed in an Array
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Result of the function call
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-10 15:20:39 -07:00
|
|
|
nvim_call_function({fn}, {args}) *nvim_call_function()*
|
|
|
|
Calls a VimL function with the given arguments.
|
|
|
|
|
|
|
|
On execution error: fails with VimL error, does not update
|
|
|
|
v:errmsg.
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2018-06-10 15:20:39 -07:00
|
|
|
{fn} Function to call
|
|
|
|
{args} Function arguments packed in an Array
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2018-06-10 15:20:39 -07:00
|
|
|
Result of the function call
|
|
|
|
|
2021-03-15 01:58:39 -07:00
|
|
|
nvim_chan_send({chan}, {data}) *nvim_chan_send()*
|
|
|
|
Send data to channel `id` . For a job, it writes it to the
|
|
|
|
stdin of the process. For the stdio channel |channel-stdio|,
|
|
|
|
it writes to Nvim's stdout. For an internal terminal instance
|
|
|
|
(|nvim_open_term()|) it writes directly to terimal output. See
|
|
|
|
|channel-bytes| for more information.
|
|
|
|
|
|
|
|
This function writes raw data, not RPC messages. If the
|
|
|
|
channel was created with `rpc=true` then the channel expects
|
|
|
|
RPC messages, use |vim.rpcnotify()| and |vim.rpcrequest()|
|
|
|
|
instead.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{chan} id of the channel
|
|
|
|
{data} data to write. 8-bit clean: can contain NUL bytes.
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_command({command}) *nvim_command()*
|
|
|
|
Executes an ex-command.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
|
|
|
On execution error: fails with VimL error, does not update
|
|
|
|
v:errmsg.
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{command} Ex-command string
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
|nvim_exec()|
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_create_buf({listed}, {scratch}) *nvim_create_buf()*
|
|
|
|
Creates a new, empty, unnamed buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{listed} Sets 'buflisted'
|
|
|
|
{scratch} Creates a "throwaway" |scratch-buffer| for
|
2020-07-02 04:09:17 -07:00
|
|
|
temporary work (always 'nomodified'). Also sets
|
|
|
|
'nomodeline' on the buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Buffer handle, or 0 on error
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
buf_open_scratch
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_create_namespace({name}) *nvim_create_namespace()*
|
|
|
|
Creates a new namespace, or gets an existing one.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Namespaces are used for buffer highlights and virtual text,
|
|
|
|
see |nvim_buf_add_highlight()| and
|
|
|
|
|nvim_buf_set_virtual_text()|.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Namespaces can be named or anonymous. If `name` matches an
|
|
|
|
existing namespace, the associated id is returned. If `name`
|
|
|
|
is an empty string a new, anonymous namespace is created.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{name} Namespace name or empty string
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Namespace id
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_del_current_line() *nvim_del_current_line()*
|
2019-01-10 17:20:15 -07:00
|
|
|
Deletes the current line.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_del_keymap({mode}, {lhs}) *nvim_del_keymap()*
|
|
|
|
Unmaps a global |mapping| for the given mode.
|
|
|
|
|
|
|
|
To unmap a buffer-local mapping, use |nvim_buf_del_keymap()|.
|
|
|
|
|
|
|
|
See also: ~
|
|
|
|
|nvim_set_keymap()|
|
|
|
|
|
|
|
|
nvim_del_var({name}) *nvim_del_var()*
|
|
|
|
Removes a global (g:) variable.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
{name} Variable name
|
|
|
|
|
2021-01-10 23:18:51 -07:00
|
|
|
nvim_echo({chunks}, {history}, {opts}) *nvim_echo()*
|
|
|
|
Echo a message.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{chunks} A list of [text, hl_group] arrays, each
|
|
|
|
representing a text chunk with specified
|
|
|
|
highlight. `hl_group` element can be omitted
|
|
|
|
for no highlight.
|
|
|
|
{history} if true, add to |message-history|.
|
|
|
|
{opts} Optional parameters. Reserved for future use.
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_err_write({str}) *nvim_err_write()*
|
|
|
|
Writes a message to the Vim error buffer. Does not append
|
|
|
|
"\n", the message is buffered (won't display) until a linefeed
|
|
|
|
is written.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{str} Message
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_err_writeln({str}) *nvim_err_writeln()*
|
|
|
|
Writes a message to the Vim error buffer. Appends "\n", so the
|
|
|
|
buffer is flushed (and displayed).
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{str} Message
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
nvim_err_write()
|
|
|
|
|
|
|
|
nvim_eval({expr}) *nvim_eval()*
|
|
|
|
Evaluates a VimL |expression|. Dictionaries and Lists are
|
|
|
|
recursively expanded.
|
|
|
|
|
|
|
|
On execution error: fails with VimL error, does not update
|
|
|
|
v:errmsg.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{expr} VimL expression string
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Evaluation result or expanded object
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_exec({src}, {output}) *nvim_exec()*
|
|
|
|
Executes Vimscript (multiline block of Ex-commands), like
|
|
|
|
anonymous |:source|.
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Unlike |nvim_command()| this function supports heredocs,
|
|
|
|
script-scope (s:), etc.
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
On execution error: fails with VimL error, does not update
|
|
|
|
v:errmsg.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{src} Vimscript code
|
|
|
|
{output} Capture and return all (non-error, non-shell
|
|
|
|
|:!|) output
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Output (non-error, non-shell |:!|) if `output` is true,
|
|
|
|
else empty string.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
|execute()|
|
|
|
|
|nvim_command()|
|
|
|
|
|
|
|
|
nvim_exec_lua({code}, {args}) *nvim_exec_lua()*
|
|
|
|
Execute Lua code. Parameters (if any) are available as `...`
|
|
|
|
inside the chunk. The chunk can return a value.
|
|
|
|
|
|
|
|
Only statements are executed. To evaluate an expression,
|
|
|
|
prefix it with `return` : return my_function(...)
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{code} Lua code to execute
|
|
|
|
{args} Arguments to the code
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Return value of Lua code if present or NIL.
|
|
|
|
|
|
|
|
nvim_feedkeys({keys}, {mode}, {escape_csi}) *nvim_feedkeys()*
|
|
|
|
Sends input-keys to Nvim, subject to various quirks controlled
|
|
|
|
by `mode` flags. This is a blocking call, unlike
|
|
|
|
|nvim_input()|.
|
|
|
|
|
|
|
|
On execution error: does not fail, but updates v:errmsg.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-08-19 09:17:08 -07:00
|
|
|
If you need to input sequences like <C-o> use
|
|
|
|
|nvim_replace_termcodes| to replace the termcodes and then
|
|
|
|
pass the resulting string to nvim_feedkeys. You'll also want
|
|
|
|
to enable escape_csi.
|
2020-07-01 18:57:03 -07:00
|
|
|
|
|
|
|
Example: >
|
2020-08-19 09:17:08 -07:00
|
|
|
:let key = nvim_replace_termcodes("<C-o>", v:true, v:false, v:true)
|
|
|
|
:call nvim_feedkeys(key, 'n', v:true)
|
2020-07-01 18:57:03 -07:00
|
|
|
<
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{keys} to be typed
|
|
|
|
{mode} behavior flags, see |feedkeys()|
|
|
|
|
{escape_csi} If true, escape K_SPECIAL/CSI bytes in
|
|
|
|
`keys`
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
feedkeys()
|
|
|
|
vim_strsave_escape_csi
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
nvim_get_all_options_info() *nvim_get_all_options_info()*
|
|
|
|
Gets the option information for all options.
|
|
|
|
|
|
|
|
The dictionary has the full option names as keys and option
|
|
|
|
metadata dictionaries as detailed at |nvim_get_option_info|.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
dictionary of all options
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_api_info() *nvim_get_api_info()*
|
|
|
|
Returns a 2-tuple (Array), where item 0 is the current channel
|
|
|
|
id and item 1 is the |api-metadata| map (Dictionary).
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
2-tuple [{channel-id}, {api-metadata}]
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
|
|
|
nvim_get_chan_info({chan}) *nvim_get_chan_info()*
|
|
|
|
Get information about a channel.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Dictionary describing a channel, with these keys:
|
|
|
|
• "stream" the stream underlying the channel
|
|
|
|
• "stdio" stdin and stdout of this Nvim instance
|
|
|
|
• "stderr" stderr of this Nvim instance
|
|
|
|
• "socket" TCP/IP socket or named pipe
|
|
|
|
• "job" job with communication over its stdio
|
|
|
|
|
|
|
|
• "mode" how data received on the channel is interpreted
|
|
|
|
• "bytes" send and receive raw bytes
|
|
|
|
• "terminal" a |terminal| instance interprets ASCII
|
|
|
|
sequences
|
|
|
|
• "rpc" |RPC| communication on the channel is active
|
|
|
|
|
|
|
|
• "pty" Name of pseudoterminal, if one is used (optional).
|
|
|
|
On a POSIX system, this will be a device path like
|
|
|
|
/dev/pts/1. Even if the name is unknown, the key will
|
|
|
|
still be present to indicate a pty is used. This is
|
|
|
|
currently the case when using winpty on windows.
|
|
|
|
• "buffer" buffer with connected |terminal| instance
|
|
|
|
(optional)
|
|
|
|
• "client" information about the client on the other end
|
|
|
|
of the RPC channel, if it has added it using
|
|
|
|
|nvim_set_client_info()|. (optional)
|
|
|
|
|
|
|
|
nvim_get_color_by_name({name}) *nvim_get_color_by_name()*
|
|
|
|
Returns the 24-bit RGB value of a |nvim_get_color_map()| color
|
|
|
|
name or "#rrggbb" hexadecimal string.
|
|
|
|
|
|
|
|
Example: >
|
|
|
|
:echo nvim_get_color_by_name("Pink")
|
|
|
|
:echo nvim_get_color_by_name("#cbcbcb")
|
|
|
|
<
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Color name or "#rrggbb" string
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
24-bit RGB value, or -1 for invalid argument.
|
|
|
|
|
|
|
|
nvim_get_color_map() *nvim_get_color_map()*
|
|
|
|
Returns a map of color names and RGB values.
|
|
|
|
|
|
|
|
Keys are color names (e.g. "Aqua") and values are 24-bit RGB
|
|
|
|
color values (e.g. 65535).
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Map of color names and RGB values.
|
|
|
|
|
|
|
|
nvim_get_commands({opts}) *nvim_get_commands()*
|
|
|
|
Gets a map of global (non-buffer-local) Ex commands.
|
|
|
|
|
|
|
|
Currently only |user-commands| are supported, not builtin Ex
|
|
|
|
commands.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{opts} Optional parameters. Currently only supports
|
|
|
|
{"builtin":false}
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Map of maps describing commands.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_context({opts}) *nvim_get_context()*
|
|
|
|
Gets a map of the current editor state.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{opts} Optional parameters.
|
|
|
|
• types: List of |context-types| ("regs", "jumps",
|
|
|
|
"bufs", "gvars", …) to gather, or empty for
|
|
|
|
"all".
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
map of global |context|.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_get_current_buf() *nvim_get_current_buf()*
|
2019-01-10 17:20:15 -07:00
|
|
|
Gets the current buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Buffer handle
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_current_line() *nvim_get_current_line()*
|
|
|
|
Gets the current line.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Current line string
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_current_tabpage() *nvim_get_current_tabpage()*
|
|
|
|
Gets the current tabpage.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Tabpage handle
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_get_current_win() *nvim_get_current_win()*
|
2019-01-10 17:20:15 -07:00
|
|
|
Gets the current window.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Window handle
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_hl_by_id({hl_id}, {rgb}) *nvim_get_hl_by_id()*
|
|
|
|
Gets a highlight definition by id. |hlID()|
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{hl_id} Highlight id as returned by |hlID()|
|
|
|
|
{rgb} Export RGB colors
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Highlight definition map
|
|
|
|
|
|
|
|
See also: ~
|
|
|
|
nvim_get_hl_by_name
|
|
|
|
|
|
|
|
nvim_get_hl_by_name({name}, {rgb}) *nvim_get_hl_by_name()*
|
|
|
|
Gets a highlight definition by name.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Highlight group name
|
|
|
|
{rgb} Export RGB colors
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Highlight definition map
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-03-03 07:01:16 -07:00
|
|
|
See also: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_hl_by_id
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_hl_id_by_name({name}) *nvim_get_hl_id_by_name()*
|
|
|
|
Gets a highlight group by name
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
similar to |hlID()|, but allocates a new ID if not present.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_keymap({mode}) *nvim_get_keymap()*
|
|
|
|
Gets a list of global (non-buffer-local) |mapping|
|
|
|
|
definitions.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{mode} Mode short-name ("n", "i", "v", ...)
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Array of maparg()-like dictionaries describing mappings.
|
|
|
|
The "buffer" key is always zero.
|
|
|
|
|
|
|
|
nvim_get_mode() *nvim_get_mode()*
|
|
|
|
Gets the current mode. |mode()| "blocking" is true if Nvim is
|
|
|
|
waiting for input.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Dictionary { "mode": String, "blocking": Boolean }
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
|
|
|
nvim_get_namespaces() *nvim_get_namespaces()*
|
|
|
|
Gets existing, non-anonymous namespaces.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
dict that maps from names to namespace ids.
|
|
|
|
|
|
|
|
nvim_get_option({name}) *nvim_get_option()*
|
|
|
|
Gets an option value string.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{name} Option name
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Option value (global)
|
|
|
|
|
2020-12-03 18:59:36 -07:00
|
|
|
nvim_get_option_info({name}) *nvim_get_option_info()*
|
|
|
|
Gets the option information for one option
|
|
|
|
|
|
|
|
Resulting dictionary has keys:
|
2020-11-24 05:37:29 -07:00
|
|
|
• name: Name of the option (like 'filetype')
|
|
|
|
• shortname: Shortened name of the option (like 'ft')
|
|
|
|
• type: type of option ("string", "integer" or "boolean")
|
|
|
|
• default: The default value for the option
|
|
|
|
• was_set: Whether the option was set.
|
|
|
|
• last_set_sid: Last set script id (if any)
|
|
|
|
• last_set_linenr: line number where option was set
|
|
|
|
• last_set_chan: Channel where option was set (0 for local)
|
|
|
|
• scope: one of "global", "win", or "buf"
|
|
|
|
• global_local: whether win or buf option has a global value
|
|
|
|
• commalist: List of comma separated values
|
|
|
|
• flaglist: List of single char flags
|
2020-12-03 18:59:36 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{name} Option name
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Option Information
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_proc({pid}) *nvim_get_proc()*
|
|
|
|
Gets info describing process `pid` .
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Map of process properties, or NIL if process not found.
|
|
|
|
|
|
|
|
nvim_get_proc_children({pid}) *nvim_get_proc_children()*
|
|
|
|
Gets the immediate children of process `pid` .
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Array of child process ids, empty if process not found.
|
|
|
|
|
2020-07-02 04:09:17 -07:00
|
|
|
nvim_get_runtime_file({name}, {all}) *nvim_get_runtime_file()*
|
|
|
|
Find files in runtime directories
|
|
|
|
|
|
|
|
'name' can contain wildcards. For example
|
|
|
|
nvim_get_runtime_file("colors/*.vim", true) will return all
|
2020-12-03 18:59:36 -07:00
|
|
|
color scheme files. Always use forward slashes (/) in the
|
|
|
|
search pattern for subdirectories regardless of platform.
|
2020-07-02 04:09:17 -07:00
|
|
|
|
|
|
|
It is not an error to not find any files. An empty array is
|
|
|
|
returned then.
|
|
|
|
|
2020-12-03 18:59:36 -07:00
|
|
|
To find a directory, `name` must end with a forward slash,
|
|
|
|
like "rplugin/python/". Without the slash it would instead
|
|
|
|
look for an ordinary file called "rplugin/python".
|
|
|
|
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
2020-07-02 04:09:17 -07:00
|
|
|
Parameters: ~
|
|
|
|
{name} pattern of files to search for
|
|
|
|
{all} whether to return all matches or only the first
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
list of absolute paths to the found files
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_get_var({name}) *nvim_get_var()*
|
|
|
|
Gets a global (g:) variable.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{name} Variable name
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Variable value
|
|
|
|
|
|
|
|
nvim_get_vvar({name}) *nvim_get_vvar()*
|
|
|
|
Gets a v: variable.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{name} Variable name
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Variable value
|
|
|
|
|
|
|
|
nvim_input({keys}) *nvim_input()*
|
|
|
|
Queues raw user-input. Unlike |nvim_feedkeys()|, this uses a
|
|
|
|
low-level input buffer and the call is non-blocking (input is
|
|
|
|
processed asynchronously by the eventloop).
|
|
|
|
|
|
|
|
On execution error: does not fail, but updates v:errmsg.
|
|
|
|
|
|
|
|
Note:
|
|
|
|
|keycodes| like <CR> are translated, so "<" is special. To
|
|
|
|
input a literal "<", send <LT>.
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Note:
|
|
|
|
For mouse events use |nvim_input_mouse()|. The pseudokey
|
|
|
|
form "<LeftMouse><col,row>" is deprecated since
|
|
|
|
|api-level| 6.
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{keys} to be typed
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Number of bytes actually written (can be fewer than
|
|
|
|
requested if the buffer becomes full).
|
|
|
|
|
|
|
|
*nvim_input_mouse()*
|
|
|
|
nvim_input_mouse({button}, {action}, {modifier}, {grid}, {row}, {col})
|
|
|
|
Send mouse event from GUI.
|
|
|
|
|
|
|
|
Non-blocking: does not wait on any result, but queues the
|
|
|
|
event to be processed soon by the event loop.
|
|
|
|
|
|
|
|
Note:
|
|
|
|
Currently this doesn't support "scripting" multiple mouse
|
|
|
|
events by calling it multiple times in a loop: the
|
|
|
|
intermediate mouse positions will be ignored. It should be
|
|
|
|
used to implement real-time mouse input in a GUI. The
|
|
|
|
deprecated pseudokey form ("<LeftMouse><col,row>") of
|
|
|
|
|nvim_input()| has the same limitiation.
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{button} Mouse button: one of "left", "right",
|
|
|
|
"middle", "wheel".
|
|
|
|
{action} For ordinary buttons, one of "press", "drag",
|
|
|
|
"release". For the wheel, one of "up", "down",
|
|
|
|
"left", "right".
|
|
|
|
{modifier} String of modifiers each represented by a
|
|
|
|
single char. The same specifiers are used as
|
|
|
|
for a key press, except that the "-" separator
|
|
|
|
is optional, so "C-A-", "c-a" and "CA" can all
|
|
|
|
be used to specify Ctrl+Alt+click.
|
|
|
|
{grid} Grid number if the client uses |ui-multigrid|,
|
|
|
|
else 0.
|
|
|
|
{row} Mouse row-position (zero-based, like redraw
|
|
|
|
events)
|
|
|
|
{col} Mouse column-position (zero-based, like redraw
|
|
|
|
events)
|
|
|
|
|
|
|
|
nvim_list_bufs() *nvim_list_bufs()*
|
|
|
|
Gets the current list of buffer handles
|
|
|
|
|
|
|
|
Includes unlisted (unloaded/deleted) buffers, like `:ls!` .
|
|
|
|
Use |nvim_buf_is_loaded()| to check if a buffer is loaded.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
List of buffer handles
|
|
|
|
|
|
|
|
nvim_list_chans() *nvim_list_chans()*
|
|
|
|
Get information about all open channels.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Array of Dictionaries, each describing a channel with the
|
|
|
|
format specified at |nvim_get_chan_info()|.
|
|
|
|
|
|
|
|
nvim_list_runtime_paths() *nvim_list_runtime_paths()*
|
|
|
|
Gets the paths contained in 'runtimepath'.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
List of paths
|
|
|
|
|
|
|
|
nvim_list_tabpages() *nvim_list_tabpages()*
|
|
|
|
Gets the current list of tabpage handles.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
List of tabpage handles
|
|
|
|
|
|
|
|
nvim_list_uis() *nvim_list_uis()*
|
|
|
|
Gets a list of dictionaries representing attached UIs.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Array of UI dictionaries, each with these keys:
|
|
|
|
• "height" Requested height of the UI
|
|
|
|
• "width" Requested width of the UI
|
|
|
|
• "rgb" true if the UI uses RGB colors (false implies
|
|
|
|
|cterm-colors|)
|
|
|
|
• "ext_..." Requested UI extensions, see |ui-option|
|
|
|
|
• "chan" Channel id of remote UI (not present for TUI)
|
|
|
|
|
|
|
|
nvim_list_wins() *nvim_list_wins()*
|
|
|
|
Gets the current list of window handles.
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
List of window handles
|
|
|
|
|
|
|
|
nvim_load_context({dict}) *nvim_load_context()*
|
|
|
|
Sets the current editor state from the given |context| map.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{dict} |Context| map.
|
|
|
|
|
2021-02-15 01:26:34 -07:00
|
|
|
nvim_notify({msg}, {log_level}, {opts}) *nvim_notify()*
|
|
|
|
Notify the user with a message
|
|
|
|
|
|
|
|
Relays the call to vim.notify . By default forwards your
|
|
|
|
message in the echo area but can be overriden to trigger
|
|
|
|
desktop notifications.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{msg} Message to display to the user
|
|
|
|
{log_level} The log level
|
|
|
|
{opts} Reserved for future use.
|
|
|
|
|
2021-03-15 01:58:39 -07:00
|
|
|
nvim_open_term({buffer}, {opts}) *nvim_open_term()*
|
|
|
|
Open a terminal instance in a buffer
|
|
|
|
|
|
|
|
By default (and currently the only option) the terminal will
|
|
|
|
not be connected to an external process. Instead, input send
|
|
|
|
on the channel will be echoed directly by the terminal. This
|
|
|
|
is useful to disply ANSI terminal sequences returned as part
|
|
|
|
of a rpc message, or similar.
|
|
|
|
|
|
|
|
Note: to directly initiate the terminal using the right size,
|
|
|
|
display the buffer in a configured window before calling this.
|
|
|
|
For instance, for a floating display, first create an empty
|
|
|
|
buffer using |nvim_create_buf()|, then display it using
|
|
|
|
|nvim_open_win()|, and then call this function. Then
|
|
|
|
|nvim_chan_send()| cal be called immediately to process
|
|
|
|
sequences in a virtual terminal having the intended size.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{buffer} the buffer to use (expected to be empty)
|
|
|
|
{opts} Optional parameters. Reserved for future use.
|
|
|
|
|
2021-04-24 03:47:52 -07:00
|
|
|
Return: ~
|
|
|
|
Channel id, or 0 on error
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_open_win({buffer}, {enter}, {config}) *nvim_open_win()*
|
|
|
|
Open a new window.
|
|
|
|
|
|
|
|
Currently this is used to open floating and external windows.
|
|
|
|
Floats are windows that are drawn above the split layout, at
|
|
|
|
some anchor position in some other window. Floats can be drawn
|
|
|
|
internally or by external GUI with the |ui-multigrid|
|
|
|
|
extension. External windows are only supported with multigrid
|
|
|
|
GUIs, and are displayed as separate top-level windows.
|
|
|
|
|
|
|
|
For a general overview of floats, see |api-floatwin|.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
Exactly one of `external` and `relative` must be specified.
|
2019-04-08 14:08:01 -07:00
|
|
|
The `width` and `height` of the new window must be specified.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-09-09 15:35:30 -07:00
|
|
|
With relative=editor (row=0,col=0) refers to the top-left
|
|
|
|
corner of the screen-grid and (row=Lines-1,col=Columns-1)
|
|
|
|
refers to the bottom-right corner. Fractional values are
|
|
|
|
allowed, but the builtin implementation (used by non-multigrid
|
|
|
|
UIs) will always round down to nearest integer.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
Out-of-bounds values, and configurations that make the float
|
|
|
|
not fit inside the main editor, are allowed. The builtin
|
2019-09-09 15:35:30 -07:00
|
|
|
implementation truncates values so floats are fully within the
|
|
|
|
main screen grid. External GUIs could let floats hover outside
|
|
|
|
of the main window like a tooltip, but this should not be used
|
|
|
|
to specify arbitrary WM screen positions.
|
|
|
|
|
|
|
|
Example (Lua): window-relative float >
|
|
|
|
vim.api.nvim_open_win(0, false,
|
|
|
|
{relative='win', row=3, col=3, width=12, height=3})
|
|
|
|
<
|
|
|
|
|
|
|
|
Example (Lua): buffer-relative float (travels as buffer is
|
|
|
|
scrolled) >
|
|
|
|
vim.api.nvim_open_win(0, false,
|
|
|
|
{relative='win', width=12, height=3, bufpos={100,10}})
|
|
|
|
<
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-09-09 15:35:30 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer to display, or 0 for current buffer
|
|
|
|
{enter} Enter the window (make it the current window)
|
|
|
|
{config} Map defining the window configuration. Keys:
|
2019-12-24 01:04:14 -07:00
|
|
|
• `relative`: Sets the window layout to "floating", placed
|
2019-10-27 15:05:59 -07:00
|
|
|
at (row,col) coordinates relative to:
|
2019-09-09 15:35:30 -07:00
|
|
|
• "editor" The global editor grid
|
|
|
|
• "win" Window given by the `win` field, or
|
2019-10-27 15:05:59 -07:00
|
|
|
current window.
|
2019-09-09 15:35:30 -07:00
|
|
|
• "cursor" Cursor position in current window.
|
|
|
|
|
|
|
|
• `win` : |window-ID| for relative="win".
|
2019-12-28 04:27:25 -07:00
|
|
|
• `anchor`: Decides which corner of the float to place
|
2019-09-09 15:35:30 -07:00
|
|
|
at (row,col):
|
|
|
|
• "NW" northwest (default)
|
|
|
|
• "NE" northeast
|
|
|
|
• "SW" southwest
|
|
|
|
• "SE" southeast
|
|
|
|
|
|
|
|
• `width` : Window width (in character cells).
|
2019-03-03 07:01:16 -07:00
|
|
|
Minimum of 1.
|
2019-09-09 15:35:30 -07:00
|
|
|
• `height` : Window height (in character cells).
|
2019-04-08 14:08:01 -07:00
|
|
|
Minimum of 1.
|
2019-09-09 15:35:30 -07:00
|
|
|
• `bufpos` : Places float relative to buffer
|
|
|
|
text (only when relative="win"). Takes a tuple
|
|
|
|
of zero-indexed [line, column]. `row` and
|
|
|
|
`col` if given are applied relative to this
|
|
|
|
position, else they default to `row=1` and
|
|
|
|
`col=0` (thus like a tooltip near the buffer
|
|
|
|
text).
|
|
|
|
• `row` : Row position in units of "screen cell
|
|
|
|
height", may be fractional.
|
|
|
|
• `col` : Column position in units of "screen
|
|
|
|
cell width", may be fractional.
|
|
|
|
• `focusable` : Enable focus by user actions
|
|
|
|
(wincmds, mouse events). Defaults to true.
|
|
|
|
Non-focusable windows can be entered by
|
|
|
|
|nvim_set_current_win()|.
|
2019-05-25 01:00:41 -07:00
|
|
|
• `external` : GUI should display the window as
|
2019-03-03 07:01:16 -07:00
|
|
|
an external top-level window. Currently
|
|
|
|
accepts no other positioning configuration
|
|
|
|
together with this.
|
2019-12-28 04:27:25 -07:00
|
|
|
• `style`: Configure the appearance of the window.
|
2019-08-25 16:00:52 -07:00
|
|
|
Currently only takes one non-empty value:
|
|
|
|
• "minimal" Nvim will display the window with
|
|
|
|
many UI options disabled. This is useful
|
2019-09-09 15:35:30 -07:00
|
|
|
when displaying a temporary float where the
|
2019-08-25 16:00:52 -07:00
|
|
|
text should not be edited. Disables
|
|
|
|
'number', 'relativenumber', 'cursorline',
|
2019-08-25 16:01:01 -07:00
|
|
|
'cursorcolumn', 'foldcolumn', 'spell' and
|
|
|
|
'list' options. 'signcolumn' is changed to
|
2019-11-22 02:55:04 -07:00
|
|
|
`auto` and 'colorcolumn' is cleared. The
|
|
|
|
end-of-buffer region is hidden by setting
|
2019-11-25 02:08:02 -07:00
|
|
|
`eob` flag of 'fillchars' to a space char,
|
|
|
|
and clearing the |EndOfBuffer| region in
|
2019-11-22 02:55:04 -07:00
|
|
|
'winhighlight'.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2021-04-06 05:22:33 -07:00
|
|
|
• `border`: style of (optional) window border. This can
|
|
|
|
either be a string or an array. the string
|
|
|
|
values are:
|
|
|
|
• "none" No border. This is the default
|
|
|
|
• "single" a single line box
|
|
|
|
• "double" a double line box
|
|
|
|
• "shadow" a drop shadow effect by blending
|
|
|
|
with the background. If it is an array it
|
|
|
|
should be an array of eight items or any
|
|
|
|
divisor of eight. The array will specifify
|
|
|
|
the eight chars building up the border in a
|
|
|
|
clockwise fashion starting with the top-left
|
|
|
|
corner. As, an example, the double box style
|
|
|
|
could be specified as: [ "╔", "═" ,"╗", "║",
|
|
|
|
"╝", "═", "╚", "║" ] if the number of chars
|
|
|
|
are less than eight, they will be repeated.
|
|
|
|
Thus an ASCII border could be specified as:
|
|
|
|
[ "/", "-", "\\", "|" ] or all chars the
|
|
|
|
same as: [ "x" ] An empty string can be used
|
|
|
|
to turn off a specific border, for instance:
|
|
|
|
[ "", "", "", ">", "", "", "", "<" ] will
|
|
|
|
only make vertical borders but not
|
|
|
|
horizontal ones. By default `FloatBorder`
|
|
|
|
highlight is used which links to `VertSplit`
|
|
|
|
when not defined. It could also be specified
|
|
|
|
by character: [ {"+", "MyCorner"}, {"x",
|
|
|
|
"MyBorder"} ]
|
|
|
|
|
2019-03-03 07:01:16 -07:00
|
|
|
Return: ~
|
|
|
|
Window handle, or 0 on error
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_out_write({str}) *nvim_out_write()*
|
|
|
|
Writes a message to the Vim output buffer. Does not append
|
|
|
|
"\n", the message is buffered (won't display) until a linefeed
|
|
|
|
is written.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{str} Message
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_parse_expression()*
|
|
|
|
nvim_parse_expression({expr}, {flags}, {highlight})
|
|
|
|
Parse a VimL expression.
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Attributes: ~
|
|
|
|
{fast}
|
2018-11-15 18:00:04 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{expr} Expression to parse. Always treated as a
|
|
|
|
single line.
|
|
|
|
{flags} Flags:
|
|
|
|
• "m" if multiple expressions in a row are
|
|
|
|
allowed (only the first one will be
|
|
|
|
parsed),
|
|
|
|
• "E" if EOC tokens are not allowed
|
|
|
|
(determines whether they will stop parsing
|
|
|
|
process or be recognized as an
|
|
|
|
operator/space, though also yielding an
|
|
|
|
error).
|
|
|
|
• "l" when needing to start parsing with
|
|
|
|
lvalues for ":let" or ":for". Common flag
|
|
|
|
sets:
|
|
|
|
• "m" to parse like for ":echo".
|
|
|
|
• "E" to parse like for "<C-r>=".
|
|
|
|
• empty string for ":call".
|
|
|
|
• "lm" to parse for ":let".
|
|
|
|
{highlight} If true, return value will also include
|
|
|
|
"highlight" key containing array of 4-tuples
|
|
|
|
(arrays) (Integer, Integer, Integer, String),
|
|
|
|
where first three numbers define the
|
|
|
|
highlighted region and represent line,
|
|
|
|
starting column and ending column (latter
|
|
|
|
exclusive: one should highlight region
|
|
|
|
[start_col, end_col)).
|
2018-11-15 18:00:04 -07:00
|
|
|
|
|
|
|
Return: ~
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
• AST: top-level dictionary with these keys:
|
|
|
|
• "error": Dictionary with error, present only if parser
|
|
|
|
saw some error. Contains the following keys:
|
|
|
|
• "message": String, error message in printf format,
|
|
|
|
translated. Must contain exactly one "%.*s".
|
|
|
|
• "arg": String, error message argument.
|
|
|
|
|
|
|
|
• "len": Amount of bytes successfully parsed. With flags
|
|
|
|
equal to "" that should be equal to the length of expr
|
|
|
|
string. (“Sucessfully parsed” here means “participated
|
|
|
|
in AST creation”, not “till the first error”.)
|
|
|
|
• "ast": AST, either nil or a dictionary with these
|
|
|
|
keys:
|
|
|
|
• "type": node type, one of the value names from
|
|
|
|
ExprASTNodeType stringified without "kExprNode"
|
|
|
|
prefix.
|
|
|
|
• "start": a pair [line, column] describing where node
|
|
|
|
is "started" where "line" is always 0 (will not be 0
|
|
|
|
if you will be using nvim_parse_viml() on e.g.
|
|
|
|
":let", but that is not present yet). Both elements
|
|
|
|
are Integers.
|
|
|
|
• "len": “length” of the node. This and "start" are
|
|
|
|
there for debugging purposes primary (debugging
|
|
|
|
parser and providing debug information).
|
|
|
|
• "children": a list of nodes described in top/"ast".
|
|
|
|
There always is zero, one or two children, key will
|
|
|
|
not be present if node has no children. Maximum
|
|
|
|
number of children may be found in node_maxchildren
|
|
|
|
array.
|
|
|
|
|
|
|
|
• Local values (present only for certain nodes):
|
|
|
|
• "scope": a single Integer, specifies scope for
|
|
|
|
"Option" and "PlainIdentifier" nodes. For "Option" it
|
|
|
|
is one of ExprOptScope values, for "PlainIdentifier"
|
|
|
|
it is one of ExprVarScope values.
|
|
|
|
• "ident": identifier (without scope, if any), present
|
|
|
|
for "Option", "PlainIdentifier", "PlainKey" and
|
|
|
|
"Environment" nodes.
|
|
|
|
• "name": Integer, register name (one character) or -1.
|
|
|
|
Only present for "Register" nodes.
|
|
|
|
• "cmp_type": String, comparison type, one of the value
|
|
|
|
names from ExprComparisonType, stringified without
|
|
|
|
"kExprCmp" prefix. Only present for "Comparison"
|
|
|
|
nodes.
|
|
|
|
• "ccs_strategy": String, case comparison strategy, one
|
|
|
|
of the value names from ExprCaseCompareStrategy,
|
|
|
|
stringified without "kCCStrategy" prefix. Only present
|
|
|
|
for "Comparison" nodes.
|
|
|
|
• "augmentation": String, augmentation type for
|
|
|
|
"Assignment" nodes. Is either an empty string, "Add",
|
|
|
|
"Subtract" or "Concat" for "=", "+=", "-=" or ".="
|
|
|
|
respectively.
|
|
|
|
• "invert": Boolean, true if result of comparison needs
|
|
|
|
to be inverted. Only present for "Comparison" nodes.
|
|
|
|
• "ivalue": Integer, integer value for "Integer" nodes.
|
|
|
|
• "fvalue": Float, floating-point value for "Float"
|
|
|
|
nodes.
|
|
|
|
• "svalue": String, value for "SingleQuotedString" and
|
|
|
|
"DoubleQuotedString" nodes.
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2019-08-29 15:16:19 -07:00
|
|
|
nvim_paste({data}, {crlf}, {phase}) *nvim_paste()*
|
2019-08-24 04:54:27 -07:00
|
|
|
Pastes at cursor, in any mode.
|
|
|
|
|
|
|
|
Invokes the `vim.paste` handler, which handles each mode
|
|
|
|
appropriately. Sets redo/undo. Faster than |nvim_input()|.
|
2019-08-29 15:16:19 -07:00
|
|
|
Lines break at LF ("\n").
|
2019-08-24 04:54:27 -07:00
|
|
|
|
|
|
|
Errors ('nomodifiable', `vim.paste()` failure, …) are
|
|
|
|
reflected in `err` but do not affect the return value (which
|
|
|
|
is strictly decided by `vim.paste()` ). On error, subsequent
|
|
|
|
calls are ignored ("drained") until the next paste is
|
|
|
|
initiated (phase 1 or -1).
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-08-24 04:54:27 -07:00
|
|
|
Parameters: ~
|
|
|
|
{data} Multiline input. May be binary (containing NUL
|
|
|
|
bytes).
|
2019-08-29 15:16:19 -07:00
|
|
|
{crlf} Also break lines at CR and CRLF.
|
2019-08-24 04:54:27 -07:00
|
|
|
{phase} -1: paste in a single call (i.e. without
|
|
|
|
streaming). To "stream" a paste, call `nvim_paste` sequentially with these `phase` values:
|
|
|
|
• 1: starts the paste (exactly once)
|
|
|
|
• 2: continues the paste (zero or more times)
|
|
|
|
• 3: ends the paste (exactly once)
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
|
|
|
|
• true: Client may continue pasting.
|
|
|
|
• false: Client must cancel the paste.
|
|
|
|
|
|
|
|
nvim_put({lines}, {type}, {after}, {follow}) *nvim_put()*
|
|
|
|
Puts text at cursor, in any mode.
|
|
|
|
|
|
|
|
Compare |:put| and |p| which are always linewise.
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-08-24 04:54:27 -07:00
|
|
|
Parameters: ~
|
|
|
|
{lines} |readfile()|-style list of lines.
|
|
|
|
|channel-lines|
|
2019-08-31 03:44:42 -07:00
|
|
|
{type} Edit behavior: any |getregtype()| result, or:
|
|
|
|
• "b" |blockwise-visual| mode (may include
|
|
|
|
width, e.g. "b3")
|
2019-11-25 02:08:02 -07:00
|
|
|
• "c" |charwise| mode
|
2019-08-24 04:54:27 -07:00
|
|
|
• "l" |linewise| mode
|
2019-08-31 03:44:42 -07:00
|
|
|
• "" guess by contents, see |setreg()|
|
2021-03-11 08:11:11 -07:00
|
|
|
{after} If true insert after cursor (like |p|), or
|
|
|
|
before (like |P|).
|
2021-03-06 04:54:13 -07:00
|
|
|
{follow} If true place cursor at end of inserted text.
|
2019-08-24 04:54:27 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_replace_termcodes()*
|
|
|
|
nvim_replace_termcodes({str}, {from_part}, {do_lt}, {special})
|
|
|
|
Replaces terminal codes and |keycodes| (<CR>, <Esc>, ...) in a
|
|
|
|
string with the internal representation.
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{str} String to be converted.
|
|
|
|
{from_part} Legacy Vim parameter. Usually true.
|
|
|
|
{do_lt} Also translate <lt>. Ignored if `special` is
|
|
|
|
false.
|
|
|
|
{special} Replace |keycodes|, e.g. <CR> becomes a "\n"
|
|
|
|
char.
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
2019-05-12 04:04:48 -07:00
|
|
|
See also: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
replace_termcodes
|
|
|
|
cpoptions
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_select_popupmenu_item()*
|
|
|
|
nvim_select_popupmenu_item({item}, {insert}, {finish}, {opts})
|
|
|
|
Selects an item in the completion popupmenu.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
If |ins-completion| is not active this API call is silently
|
|
|
|
ignored. Useful for an external UI using |ui-popupmenu| to
|
|
|
|
control the popupmenu with the mouse. Can also be used in a
|
|
|
|
mapping; use <cmd> |:map-cmd| to ensure the mapping doesn't
|
|
|
|
end completion mode.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{item} Index (zero-based) of the item to select. Value
|
|
|
|
of -1 selects nothing and restores the original
|
|
|
|
text.
|
|
|
|
{insert} Whether the selection should be inserted in the
|
|
|
|
buffer.
|
|
|
|
{finish} Finish the completion and dismiss the popupmenu.
|
|
|
|
Implies `insert` .
|
|
|
|
{opts} Optional parameters. Reserved for future use.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-10 15:20:39 -07:00
|
|
|
*nvim_set_client_info()*
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
nvim_set_client_info({name}, {version}, {type}, {methods}, {attributes})
|
2019-05-25 01:00:41 -07:00
|
|
|
Self-identifies the client.
|
|
|
|
|
|
|
|
The client/plugin/application should call this after
|
|
|
|
connecting, to provide hints about its identity and purpose,
|
|
|
|
for debugging and orchestration.
|
|
|
|
|
|
|
|
Can be called more than once; the caller should merge old info
|
|
|
|
if appropriate. Example: library first identifies the channel,
|
|
|
|
then a plugin using that library later identifies itself.
|
|
|
|
|
|
|
|
Note:
|
|
|
|
"Something is better than nothing". You don't need to
|
|
|
|
include all the fields.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{name} Short name for the connected client
|
|
|
|
{version} Dictionary describing the version, with
|
|
|
|
these (optional) keys:
|
2019-05-25 01:00:41 -07:00
|
|
|
• "major" major version (defaults to 0 if
|
2019-03-03 07:01:16 -07:00
|
|
|
not set, for no release yet)
|
2019-05-25 01:00:41 -07:00
|
|
|
• "minor" minor version
|
|
|
|
• "patch" patch number
|
|
|
|
• "prerelease" string describing a
|
2019-03-03 07:01:16 -07:00
|
|
|
prerelease, like "dev" or "beta1"
|
2019-05-25 01:00:41 -07:00
|
|
|
• "commit" hash or similar identifier of
|
2019-03-03 07:01:16 -07:00
|
|
|
commit
|
|
|
|
{type} Must be one of the following values. Client
|
|
|
|
libraries should default to "remote" unless
|
|
|
|
overridden by the user.
|
2019-05-25 01:00:41 -07:00
|
|
|
• "remote" remote client connected to Nvim.
|
|
|
|
• "ui" gui frontend
|
|
|
|
• "embedder" application using Nvim as a
|
2019-03-03 07:01:16 -07:00
|
|
|
component (for example, IDE/editor
|
|
|
|
implementing a vim mode).
|
2019-05-25 01:00:41 -07:00
|
|
|
• "host" plugin host, typically started by
|
2019-03-03 07:01:16 -07:00
|
|
|
nvim
|
2019-05-25 01:00:41 -07:00
|
|
|
• "plugin" single plugin, started by nvim
|
2018-06-10 15:20:39 -07:00
|
|
|
{methods} Builtin methods in the client. For a host,
|
|
|
|
this does not include plugin methods which
|
|
|
|
will be discovered later. The key should be
|
|
|
|
the method name, the values are dicts with
|
2019-03-03 07:01:16 -07:00
|
|
|
these (optional) keys (more keys may be
|
|
|
|
added in future versions of Nvim, thus
|
|
|
|
unknown keys are ignored. Clients must only
|
|
|
|
use keys defined in this or later versions
|
|
|
|
of Nvim):
|
2019-05-25 01:00:41 -07:00
|
|
|
• "async" if true, send as a notification.
|
2019-03-03 07:01:16 -07:00
|
|
|
If false or unspecified, use a blocking
|
|
|
|
request
|
2019-05-25 01:00:41 -07:00
|
|
|
• "nargs" Number of arguments. Could be a
|
2019-03-03 07:01:16 -07:00
|
|
|
single integer or an array of two
|
|
|
|
integers, minimum and maximum inclusive.
|
|
|
|
{attributes} Arbitrary string:string map of informal
|
|
|
|
client properties. Suggested keys:
|
2019-05-25 01:00:41 -07:00
|
|
|
• "website": Client homepage URL (e.g.
|
2019-03-03 07:01:16 -07:00
|
|
|
GitHub repository)
|
2019-05-25 01:00:41 -07:00
|
|
|
• "license": License description ("Apache
|
2019-03-03 07:01:16 -07:00
|
|
|
2", "GPLv3", "MIT", …)
|
2019-05-25 01:00:41 -07:00
|
|
|
• "logo": URI or path to image, preferably
|
2019-03-03 07:01:16 -07:00
|
|
|
small logo or icon. .png or .svg format is
|
|
|
|
preferred.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_current_buf({buffer}) *nvim_set_current_buf()*
|
|
|
|
Sets the current buffer.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_current_dir({dir}) *nvim_set_current_dir()*
|
|
|
|
Changes the global working directory.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{dir} Directory path
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_current_line({line}) *nvim_set_current_line()*
|
|
|
|
Sets the current line.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{line} Line contents
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_current_tabpage({tabpage}) *nvim_set_current_tabpage()*
|
|
|
|
Sets the current tabpage.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{tabpage} Tabpage handle
|
2017-11-14 02:47:49 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_current_win({window}) *nvim_set_current_win()*
|
|
|
|
Sets the current window.
|
2017-11-14 02:47:49 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{window} Window handle
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2020-10-20 12:57:07 -07:00
|
|
|
*nvim_set_decoration_provider()*
|
|
|
|
nvim_set_decoration_provider({ns_id}, {opts})
|
|
|
|
Set or change decoration provider for a namespace
|
|
|
|
|
|
|
|
This is a very general purpose interface for having lua
|
|
|
|
callbacks being triggered during the redraw code.
|
|
|
|
|
|
|
|
The expected usage is to set extmarks for the currently
|
|
|
|
redrawn buffer. |nvim_buf_set_extmark| can be called to add
|
|
|
|
marks on a per-window or per-lines basis. Use the `ephemeral`
|
|
|
|
key to only use the mark for the current screen redraw (the
|
|
|
|
callback will be called again for the next redraw ).
|
|
|
|
|
|
|
|
Note: this function should not be called often. Rather, the
|
|
|
|
callbacks themselves can be used to throttle unneeded
|
|
|
|
callbacks. the `on_start` callback can return `false` to
|
|
|
|
disable the provider until the next redraw. Similarily, return
|
|
|
|
`false` in `on_win` will skip the `on_lines` calls for that
|
|
|
|
window (but any extmarks set in `on_win` will still be used).
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
A plugin managing multiple sources of decoration should
|
2020-10-20 12:57:07 -07:00
|
|
|
ideally only set one provider, and merge the sources
|
|
|
|
internally. You can use multiple `ns_id` for the extmarks
|
|
|
|
set/modified inside the callback anyway.
|
|
|
|
|
|
|
|
Note: doing anything other than setting extmarks is considered
|
|
|
|
experimental. Doing things like changing options are not
|
|
|
|
expliticly forbidden, but is likely to have unexpected
|
|
|
|
consequences (such as 100% CPU consumption). doing
|
|
|
|
`vim.rpcnotify` should be OK, but `vim.rpcrequest` is quite
|
|
|
|
dubious for the moment.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{ns_id} Namespace id from |nvim_create_namespace()|
|
|
|
|
{opts} Callbacks invoked during redraw:
|
|
|
|
• on_start: called first on each screen redraw
|
|
|
|
["start", tick]
|
|
|
|
• on_buf: called for each buffer being redrawn
|
|
|
|
(before window callbacks) ["buf", bufnr, tick]
|
|
|
|
• on_win: called when starting to redraw a
|
|
|
|
specific window. ["win", winid, bufnr, topline,
|
|
|
|
botline_guess]
|
|
|
|
• on_line: called for each buffer line being
|
|
|
|
redrawn. (The interation with fold lines is
|
|
|
|
subject to change) ["win", winid, bufnr, row]
|
|
|
|
• on_end: called at the end of a redraw cycle
|
|
|
|
["end", tick]
|
|
|
|
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
nvim_set_hl({ns_id}, {name}, {val}) *nvim_set_hl()*
|
|
|
|
Set a highlight group.
|
|
|
|
|
|
|
|
TODO: ns_id = 0, should modify :highlight namespace TODO val
|
|
|
|
should take update vs reset flag
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{ns_id} number of namespace for this highlight
|
|
|
|
{name} highlight group name, like ErrorMsg
|
|
|
|
{val} highlight definiton map, like
|
2020-12-03 18:59:36 -07:00
|
|
|
|nvim_get_hl_by_name|. in addition the following
|
|
|
|
keys are also recognized: `default` : don't
|
|
|
|
override existing definition, like `hi default`
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_keymap({mode}, {lhs}, {rhs}, {opts}) *nvim_set_keymap()*
|
|
|
|
Sets a global |mapping| for the given mode.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
To set a buffer-local mapping, use |nvim_buf_set_keymap()|.
|
2019-03-03 07:01:16 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Unlike |:map|, leading/trailing whitespace is accepted as part
|
|
|
|
of the {lhs} or {rhs}. Empty {rhs} is |<Nop>|. |keycodes| are
|
|
|
|
replaced as usual.
|
2017-11-14 02:47:49 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Example: >
|
|
|
|
call nvim_set_keymap('n', ' <NL>', '', {'nowait': v:true})
|
|
|
|
<
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
is equivalent to: >
|
|
|
|
nmap <nowait> <Space><NL> <Nop>
|
|
|
|
<
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{mode} Mode short-name (map command prefix: "n", "i",
|
|
|
|
"v", "x", …) or "!" for |:map!|, or empty string
|
|
|
|
for |:map|.
|
|
|
|
{lhs} Left-hand-side |{lhs}| of the mapping.
|
|
|
|
{rhs} Right-hand-side |{rhs}| of the mapping.
|
|
|
|
{opts} Optional parameters map. Accepts all
|
|
|
|
|:map-arguments| as keys excluding |<buffer>| but
|
|
|
|
including |noremap|. Values are Booleans. Unknown
|
|
|
|
key is an error.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_option({name}, {value}) *nvim_set_option()*
|
|
|
|
Sets an option value.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Option name
|
|
|
|
{value} New option value
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_var({name}, {value}) *nvim_set_var()*
|
|
|
|
Sets a global (g:) variable.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
|
|
|
{value} Variable value
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_set_vvar({name}, {value}) *nvim_set_vvar()*
|
|
|
|
Sets a v: variable, if it is not readonly.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
|
|
|
{value} Variable value
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_strwidth({text}) *nvim_strwidth()*
|
|
|
|
Calculates the number of display cells occupied by `text` .
|
|
|
|
<Tab> counts as one cell.
|
2019-01-10 17:20:15 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{text} Some text
|
2019-01-10 17:20:15 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Number of cells
|
2018-07-24 21:13:51 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_subscribe({event}) *nvim_subscribe()*
|
|
|
|
Subscribes to event broadcasts.
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{event} Event type string
|
|
|
|
|
|
|
|
nvim_unsubscribe({event}) *nvim_unsubscribe()*
|
|
|
|
Unsubscribes to event broadcasts.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{event} Event type string
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
==============================================================================
|
|
|
|
Buffer Functions *api-buffer*
|
|
|
|
|
2020-07-02 04:09:17 -07:00
|
|
|
|
|
|
|
For more information on buffers, see |buffers|.
|
|
|
|
|
2018-07-24 21:13:51 -07:00
|
|
|
Unloaded Buffers:~
|
|
|
|
|
|
|
|
Buffers may be unloaded by the |:bunload| command or the
|
|
|
|
buffer's |'bufhidden'| option. When a buffer is unloaded its
|
|
|
|
file contents are freed from memory and vim cannot operate on
|
|
|
|
the buffer lines until it is reloaded (usually by opening the
|
|
|
|
buffer again in a new window). API methods such as
|
|
|
|
|nvim_buf_get_lines()| and |nvim_buf_line_count()| will be
|
|
|
|
affected.
|
|
|
|
|
|
|
|
You can use |nvim_buf_is_loaded()| or |nvim_buf_line_count()|
|
|
|
|
to check whether a buffer is loaded.
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim__buf_redraw_range()*
|
|
|
|
nvim__buf_redraw_range({buffer}, {first}, {last})
|
|
|
|
TODO: Documentation
|
|
|
|
|
|
|
|
nvim__buf_stats({buffer}) *nvim__buf_stats()*
|
|
|
|
TODO: Documentation
|
|
|
|
|
|
|
|
*nvim_buf_add_highlight()*
|
2021-03-11 08:11:11 -07:00
|
|
|
nvim_buf_add_highlight({buffer}, {ns_id}, {hl_group}, {line}, {col_start},
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
{col_end})
|
2019-12-28 04:27:25 -07:00
|
|
|
Adds a highlight to buffer.
|
|
|
|
|
|
|
|
Useful for plugins that dynamically generate highlights to a
|
|
|
|
buffer (like a semantic highlighter or linter). The function
|
|
|
|
adds a single highlight to a buffer. Unlike |matchaddpos()|
|
|
|
|
highlights follow changes to line numbering (as lines are
|
|
|
|
inserted/removed above the highlighted line), like signs and
|
|
|
|
marks do.
|
|
|
|
|
|
|
|
Namespaces are used for batch deletion/updating of a set of
|
2020-09-05 22:10:56 -07:00
|
|
|
highlights. To create a namespace, use
|
|
|
|
|nvim_create_namespace()| which returns a namespace id. Pass
|
|
|
|
it in to this function as `ns_id` to add highlights to the
|
|
|
|
namespace. All highlights in the same namespace can then be
|
|
|
|
cleared with single call to |nvim_buf_clear_namespace()|. If
|
|
|
|
the highlight never will be deleted by an API call, pass
|
|
|
|
`ns_id = -1` .
|
2019-12-28 04:27:25 -07:00
|
|
|
|
|
|
|
As a shorthand, `ns_id = 0` can be used to create a new
|
|
|
|
namespace for the highlight, the allocated id is then
|
|
|
|
returned. If `hl_group` is the empty string no highlight is
|
|
|
|
added, but a new `ns_id` is still returned. This is supported
|
|
|
|
for backwards compatibility, new code should use
|
2020-09-05 22:10:56 -07:00
|
|
|
|nvim_create_namespace()| to create a new empty namespace.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{ns_id} namespace to use or -1 for ungrouped
|
|
|
|
highlight
|
|
|
|
{hl_group} Name of the highlight group to use
|
|
|
|
{line} Line to highlight (zero-indexed)
|
|
|
|
{col_start} Start of (byte-indexed) column range to
|
|
|
|
highlight
|
|
|
|
{col_end} End of (byte-indexed) column range to
|
|
|
|
highlight, or -1 to highlight to end of line
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
The ns_id that was used
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-10 15:20:39 -07:00
|
|
|
nvim_buf_attach({buffer}, {send_buffer}, {opts}) *nvim_buf_attach()*
|
2019-10-27 15:05:59 -07:00
|
|
|
Activates buffer-update events on a channel, or as Lua
|
2019-08-25 16:00:52 -07:00
|
|
|
callbacks.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-11-17 20:06:59 -07:00
|
|
|
Example (Lua): capture buffer updates in a global `events` variable (use "print(vim.inspect(events))" to see its
|
|
|
|
contents): >
|
|
|
|
events = {}
|
|
|
|
vim.api.nvim_buf_attach(0, false, {
|
|
|
|
on_lines=function(...) table.insert(events, {...}) end})
|
|
|
|
<
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-10-27 15:05:59 -07:00
|
|
|
{send_buffer} True if the initial notification should
|
|
|
|
contain the whole buffer: first
|
|
|
|
notification will be `nvim_buf_lines_event`
|
|
|
|
. Else the first notification will be
|
|
|
|
`nvim_buf_changedtick_event` . Not for Lua
|
|
|
|
callbacks.
|
2019-08-25 16:01:01 -07:00
|
|
|
{opts} Optional parameters.
|
2019-10-27 15:05:59 -07:00
|
|
|
• on_lines: Lua callback invoked on change.
|
2019-12-28 04:27:25 -07:00
|
|
|
Return`true`to detach. Args:
|
2020-05-18 22:26:17 -07:00
|
|
|
• the string "lines"
|
2019-10-27 15:05:59 -07:00
|
|
|
• buffer handle
|
|
|
|
• b:changedtick
|
|
|
|
• first line that changed (zero-indexed)
|
|
|
|
• last line that was changed
|
|
|
|
• last line in the updated range
|
|
|
|
• byte count of previous contents
|
|
|
|
• deleted_codepoints (if `utf_sizes` is
|
|
|
|
true)
|
|
|
|
• deleted_codeunits (if `utf_sizes` is
|
|
|
|
true)
|
|
|
|
|
2021-02-15 01:26:34 -07:00
|
|
|
• on_bytes: lua callback invoked on change.
|
|
|
|
This callback receives more granular
|
|
|
|
information about the change compared to
|
|
|
|
on_lines. Return`true`to detach. Args:
|
|
|
|
• the string "bytes"
|
|
|
|
• buffer handle
|
|
|
|
• b:changedtick
|
|
|
|
• start row of the changed text
|
|
|
|
(zero-indexed)
|
|
|
|
• start column of the changed text
|
|
|
|
• byte offset of the changed text (from
|
|
|
|
the start of the buffer)
|
|
|
|
• old end row of the changed text
|
|
|
|
• old end column of the changed text
|
|
|
|
• old end byte length of the changed text
|
|
|
|
• new end row of the changed text
|
|
|
|
• new end column of the changed text
|
|
|
|
• new end byte length of the changed text
|
|
|
|
|
2019-10-27 15:05:59 -07:00
|
|
|
• on_changedtick: Lua callback invoked on
|
|
|
|
changedtick increment without text
|
|
|
|
change. Args:
|
2020-05-18 22:26:17 -07:00
|
|
|
• the string "changedtick"
|
2019-10-27 15:05:59 -07:00
|
|
|
• buffer handle
|
|
|
|
• b:changedtick
|
|
|
|
|
|
|
|
• on_detach: Lua callback invoked on
|
|
|
|
detach. Args:
|
2020-05-18 22:26:17 -07:00
|
|
|
• the string "detach"
|
2019-10-27 15:05:59 -07:00
|
|
|
• buffer handle
|
|
|
|
|
2021-02-15 01:26:34 -07:00
|
|
|
• on_reload: Lua callback invoked on
|
|
|
|
reload. The entire buffer content should
|
|
|
|
be considered changed. Args:
|
|
|
|
• the string "detach"
|
|
|
|
• buffer handle
|
|
|
|
|
2019-10-27 15:05:59 -07:00
|
|
|
• utf_sizes: include UTF-32 and UTF-16 size
|
|
|
|
of the replaced region, as args to
|
|
|
|
`on_lines` .
|
2021-01-01 12:24:40 -07:00
|
|
|
• preview: also attach to command preview
|
|
|
|
(i.e. 'inccommand') events.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-10-27 15:05:59 -07:00
|
|
|
False if attach failed (invalid parameter, or buffer isn't
|
|
|
|
loaded); otherwise True. TODO: LUA_API_NO_EVAL
|
|
|
|
|
|
|
|
See also: ~
|
|
|
|
|nvim_buf_detach()|
|
|
|
|
|api-buffer-updates-lua|
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2020-10-20 12:57:07 -07:00
|
|
|
nvim_buf_call({buffer}, {fun}) *nvim_buf_call()*
|
|
|
|
call a function with buffer as temporary current buffer
|
|
|
|
|
|
|
|
This temporarily switches current buffer to "buffer". If the
|
|
|
|
current window already shows "buffer", the window is not
|
|
|
|
switched If a window inside the current tabpage (including a
|
|
|
|
float) already shows the buffer One of these windows will be
|
|
|
|
set as current window temporarily. Otherwise a temporary
|
|
|
|
scratch window (calleed the "autocmd window" for historical
|
|
|
|
reasons) will be used.
|
|
|
|
|
|
|
|
This is useful e.g. to call vimL functions that only work with
|
|
|
|
the current buffer/window currently, like |termopen()|.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{fun} Function to call inside the buffer (currently
|
|
|
|
lua callable only)
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Return value of function. NB: will deepcopy lua values
|
|
|
|
currently, use upvalues to send lua references in and out.
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_clear_namespace()*
|
|
|
|
nvim_buf_clear_namespace({buffer}, {ns_id}, {line_start}, {line_end})
|
|
|
|
Clears namespaced objects (highlights, extmarks, virtual text)
|
|
|
|
from a region.
|
|
|
|
|
|
|
|
Lines are 0-indexed. |api-indexing| To clear the namespace in
|
|
|
|
the entire buffer, specify line_start=0 and line_end=-1.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{ns_id} Namespace to clear, or -1 to clear all
|
|
|
|
namespaces.
|
|
|
|
{line_start} Start of range of lines to clear
|
|
|
|
{line_end} End of range of lines to clear (exclusive)
|
|
|
|
or -1 to clear to end of buffer.
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_del_extmark({buffer}, {ns_id}, {id}) *nvim_buf_del_extmark()*
|
|
|
|
Removes an extmark.
|
2019-10-27 15:05:59 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{ns_id} Namespace id from |nvim_create_namespace()|
|
|
|
|
{id} Extmark id
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
true if the extmark was found, else false
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_del_keymap({buffer}, {mode}, {lhs}) *nvim_buf_del_keymap()*
|
|
|
|
Unmaps a buffer-local |mapping| for the given mode.
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
|nvim_del_keymap()|
|
2019-12-24 01:04:14 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_del_var({buffer}, {name}) *nvim_buf_del_var()*
|
|
|
|
Removes a buffer-scoped (b:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{name} Variable name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-10-09 12:39:59 -07:00
|
|
|
nvim_buf_delete({buffer}, {opts}) *nvim_buf_delete()*
|
|
|
|
Deletes the buffer. See |:bwipeout|
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2020-10-09 12:39:59 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{opts} Optional parameters. Keys:
|
|
|
|
• force: Force deletion and ignore unsaved
|
|
|
|
changes.
|
|
|
|
• unload: Unloaded only, do not delete. See
|
|
|
|
|:bunload|
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_detach({buffer}) *nvim_buf_detach()*
|
|
|
|
Deactivates buffer-update events on the channel.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
False if detach failed (because the buffer isn't loaded);
|
|
|
|
otherwise True.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
|nvim_buf_attach()|
|
|
|
|
|api-lua-detach| for detaching Lua callbacks
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_changedtick({buffer}) *nvim_buf_get_changedtick()*
|
|
|
|
Gets a changed tick of a buffer
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2018-11-04 19:50:22 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
`b:changedtick` value.
|
2018-11-04 19:50:22 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_commands({buffer}, {opts}) *nvim_buf_get_commands()*
|
|
|
|
Gets a map of buffer-local |user-commands|.
|
2018-11-04 19:50:22 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{opts} Optional parameters. Currently not used.
|
2018-11-04 19:50:22 -07:00
|
|
|
|
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Map of maps describing commands.
|
2018-11-04 19:50:22 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_get_extmark_by_id()*
|
2020-09-06 16:55:49 -07:00
|
|
|
nvim_buf_get_extmark_by_id({buffer}, {ns_id}, {id}, {opts})
|
2019-12-28 04:27:25 -07:00
|
|
|
Returns position for a given extmark id
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{ns_id} Namespace id from |nvim_create_namespace()|
|
|
|
|
{id} Extmark id
|
2020-09-06 16:55:49 -07:00
|
|
|
{opts} Optional parameters. Keys:
|
2021-01-18 05:32:07 -07:00
|
|
|
• details: Whether to include the details dict
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
(row, col) tuple or empty list () if extmark id was absent
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_get_extmarks()*
|
|
|
|
nvim_buf_get_extmarks({buffer}, {ns_id}, {start}, {end}, {opts})
|
|
|
|
Gets extmarks in "traversal order" from a |charwise| region
|
|
|
|
defined by buffer positions (inclusive, 0-indexed
|
|
|
|
|api-indexing|).
|
|
|
|
|
|
|
|
Region can be given as (row,col) tuples, or valid extmark ids
|
|
|
|
(whose positions define the bounds). 0 and -1 are understood
|
|
|
|
as (0,0) and (-1,-1) respectively, thus the following are
|
|
|
|
equivalent:
|
|
|
|
>
|
2020-07-02 04:09:17 -07:00
|
|
|
nvim_buf_get_extmarks(0, my_ns, 0, -1, {})
|
|
|
|
nvim_buf_get_extmarks(0, my_ns, [0,0], [-1,-1], {})
|
2019-12-28 04:27:25 -07:00
|
|
|
<
|
|
|
|
|
|
|
|
If `end` is less than `start` , traversal works backwards.
|
|
|
|
(Useful with `limit` , to get the first marks prior to a given
|
|
|
|
position.)
|
|
|
|
|
|
|
|
Example:
|
|
|
|
>
|
2020-07-02 04:09:17 -07:00
|
|
|
local a = vim.api
|
|
|
|
local pos = a.nvim_win_get_cursor(0)
|
|
|
|
local ns = a.nvim_create_namespace('my-plugin')
|
|
|
|
-- Create new extmark at line 1, column 1.
|
|
|
|
local m1 = a.nvim_buf_set_extmark(0, ns, 0, 0, 0, {})
|
|
|
|
-- Create new extmark at line 3, column 1.
|
|
|
|
local m2 = a.nvim_buf_set_extmark(0, ns, 0, 2, 0, {})
|
|
|
|
-- Get extmarks only from line 3.
|
|
|
|
local ms = a.nvim_buf_get_extmarks(0, ns, {2,0}, {2,0}, {})
|
|
|
|
-- Get all marks in this buffer + namespace.
|
|
|
|
local all = a.nvim_buf_get_extmarks(0, ns, 0, -1, {})
|
|
|
|
print(vim.inspect(ms))
|
2019-12-28 04:27:25 -07:00
|
|
|
<
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{ns_id} Namespace id from |nvim_create_namespace()|
|
|
|
|
{start} Start of range, given as (row, col) or valid
|
|
|
|
extmark id (whose position defines the bound)
|
|
|
|
{end} End of range, given as (row, col) or valid
|
|
|
|
extmark id (whose position defines the bound)
|
|
|
|
{opts} Optional parameters. Keys:
|
|
|
|
• limit: Maximum number of marks to return
|
2020-09-06 16:55:49 -07:00
|
|
|
• details Whether to include the details dict
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
List of [extmark_id, row, col] tuples in "traversal
|
|
|
|
order".
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2017-07-02 04:46:41 -07:00
|
|
|
nvim_buf_get_keymap({buffer}, {mode}) *nvim_buf_get_keymap()*
|
2018-06-10 15:20:39 -07:00
|
|
|
Gets a list of buffer-local |mapping| definitions.
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2017-11-05 18:00:39 -07:00
|
|
|
{mode} Mode short-name ("n", "i", "v", ...)
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2018-06-10 15:20:39 -07:00
|
|
|
Array of maparg()-like dictionaries describing mappings.
|
|
|
|
The "buffer" key holds the associated buffer handle.
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_get_lines()*
|
|
|
|
nvim_buf_get_lines({buffer}, {start}, {end}, {strict_indexing})
|
|
|
|
Gets a line-range from the buffer.
|
|
|
|
|
|
|
|
Indexing is zero-based, end-exclusive. Negative indices are
|
|
|
|
interpreted as length+1+index: -1 refers to the index past the
|
|
|
|
end. So to get the last element use start=-2 and end=-1.
|
|
|
|
|
|
|
|
Out-of-bounds indices are clamped to the nearest valid value,
|
|
|
|
unless `strict_indexing` is set.
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{start} First line index
|
|
|
|
{end} Last line index (exclusive)
|
|
|
|
{strict_indexing} Whether out-of-bounds should be an
|
|
|
|
error.
|
2019-05-12 04:04:48 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Array of lines, or empty array for unloaded buffer.
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_mark({buffer}, {name}) *nvim_buf_get_mark()*
|
|
|
|
Return a tuple (row,col) representing the position of the
|
|
|
|
named mark.
|
|
|
|
|
|
|
|
Marks are (1,0)-indexed. |api-indexing|
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-05-12 04:04:48 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Mark name
|
2019-05-12 04:04:48 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
(row, col) tuple
|
API: nvim_set_keymap, nvim_del_keymap #9924
closes #9136
- Treat empty {rhs} like <Nop>
- getchar.c: Pull "repl. MapArg termcodes" into func
The "preprocessing code" surrounding the replace_termcodes calls needs
to invoke replace_termcodes, and also check if RHS is equal to "<Nop>".
To reduce code duplication, factor this out into a helper function.
Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit
expects an empty {rhs} string for "<Nop>", but also needs to distinguish
that from something like ":map lhs<cr>" where no {rhs} was provided.
- getchar.c: Use allocated buffer for rhs in MapArgs
Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or
else an RHS that calls a really long autoload function from a plugin
would be incorrectly rejected as being too long), use an allocated
buffer for RHS rather than a static buffer of length MAXMAPLEN + 1.
- Mappings LHS and RHS can contain literal space characters, newlines, etc.
- getchar.c: replace_termcodes in str_to_mapargs
It makes sense to do this; str_to_mapargs is, intuitively, supposed to
take a "raw" command string and parse it into a totally "do_map-ready"
struct.
- api/vim.c: Update lhs, rhs len after replace_termcodes
Fixes a bug in which replace_termcodes changes the length of lhs or rhs,
but the later search through the mappings/abbreviations hashtables
still uses the old length value. This would cause the search to fail
erroneously and throw 'E31: No such mapping' errors or 'E24: No such
abbreviation' errors.
- getchar: Create new map_arguments struct
So that a string of map arguments can be parsed into a more useful, more
portable data structure.
- getchar.c: Add buf_do_map function
Exactly the same as the old do_map, but replace the hardcoded references
to the global `buf_T* curbuf` with a function parameter so that we can
invoke it from nvim_buf_set_keymap.
- Remove gettext calls in do_map error handling
2019-05-12 02:44:48 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_name({buffer}) *nvim_buf_get_name()*
|
|
|
|
Gets the full file name for the buffer
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2018-06-10 15:20:39 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Buffer name
|
2017-07-02 04:46:41 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_offset({buffer}, {index}) *nvim_buf_get_offset()*
|
|
|
|
Returns the byte offset of a line (0-indexed). |api-indexing|
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Line 1 (index=0) has offset 0. UTF-8 bytes are counted. EOL is
|
|
|
|
one byte. 'fileformat' and 'fileencoding' are ignored. The
|
|
|
|
line index just after the last line gives the total byte-count
|
|
|
|
of the buffer. A final EOL byte is counted if it would be
|
|
|
|
written, see 'eol'.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Unlike |line2byte()|, throws error for out-of-bounds indexing.
|
|
|
|
Returns -1 for unloaded buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{index} Line index
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Integer byte offset, or -1 for unloaded buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_buf_get_option({buffer}, {name}) *nvim_buf_get_option()*
|
|
|
|
Gets a buffer option value
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2017-03-01 09:18:03 -07:00
|
|
|
{name} Option name
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Option value
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_get_var({buffer}, {name}) *nvim_buf_get_var()*
|
|
|
|
Gets a buffer-scoped (b:) variable.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Variable value
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-07-24 21:13:51 -07:00
|
|
|
nvim_buf_is_loaded({buffer}) *nvim_buf_is_loaded()*
|
|
|
|
Checks if a buffer is valid and loaded. See |api-buffer| for
|
|
|
|
more info about unloaded buffers.
|
|
|
|
|
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2018-07-24 21:13:51 -07:00
|
|
|
|
|
|
|
Return: ~
|
|
|
|
true if the buffer is valid and loaded, false otherwise.
|
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
nvim_buf_is_valid({buffer}) *nvim_buf_is_valid()*
|
2018-07-24 21:13:51 -07:00
|
|
|
Checks if a buffer is valid.
|
|
|
|
|
|
|
|
Note:
|
|
|
|
Even if a buffer is valid it may have been unloaded. See
|
|
|
|
|api-buffer| for more info about unloaded buffers.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2018-07-24 21:13:51 -07:00
|
|
|
true if the buffer is valid, false otherwise.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_line_count({buffer}) *nvim_buf_line_count()*
|
|
|
|
Gets the buffer line count
|
2019-11-09 04:41:50 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-11-25 02:08:02 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-11-09 04:41:50 -07:00
|
|
|
|
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Line count, or 0 for unloaded buffer. |api-buffer|
|
2019-11-09 04:41:50 -07:00
|
|
|
|
|
|
|
*nvim_buf_set_extmark()*
|
2020-09-06 16:55:49 -07:00
|
|
|
nvim_buf_set_extmark({buffer}, {ns_id}, {line}, {col}, {opts})
|
2019-11-25 02:08:02 -07:00
|
|
|
Creates or updates an extmark.
|
2019-11-09 04:41:50 -07:00
|
|
|
|
2019-11-25 02:08:02 -07:00
|
|
|
To create a new extmark, pass id=0. The extmark id will be
|
2020-09-06 16:55:49 -07:00
|
|
|
returned. To move an existing mark, pass its id.
|
|
|
|
|
|
|
|
It is also allowed to create a new mark by passing in a
|
|
|
|
previously unused id, but the caller must then keep track of
|
|
|
|
existing and unused ids itself. (Useful over RPC, to avoid
|
2019-11-25 02:08:02 -07:00
|
|
|
waiting for the return value.)
|
2019-11-09 04:41:50 -07:00
|
|
|
|
2020-09-06 16:55:49 -07:00
|
|
|
Using the optional arguments, it is possible to use this to
|
|
|
|
highlight a range of text, and also to associate virtual text
|
|
|
|
to the mark.
|
|
|
|
|
2019-11-09 04:41:50 -07:00
|
|
|
Parameters: ~
|
2019-11-25 02:08:02 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{ns_id} Namespace id from |nvim_create_namespace()|
|
|
|
|
{line} Line number where to place the mark
|
|
|
|
{col} Column where to place the mark
|
2020-09-06 16:55:49 -07:00
|
|
|
{opts} Optional parameters.
|
|
|
|
• id : id of the extmark to edit.
|
|
|
|
• end_line : ending line of the mark, 0-based
|
|
|
|
inclusive.
|
|
|
|
• end_col : ending col of the mark, 0-based
|
|
|
|
inclusive.
|
|
|
|
• hl_group : name of the highlight group used to
|
|
|
|
highlight this mark.
|
|
|
|
• virt_text : virtual text to link to this mark.
|
2021-02-24 15:44:52 -07:00
|
|
|
• virt_text_pos : positioning of virtual text.
|
|
|
|
Possible values:
|
|
|
|
• "eol": right after eol character (default)
|
|
|
|
• "overlay": display over the specified
|
|
|
|
column, without shifting the underlying
|
|
|
|
text.
|
|
|
|
|
2021-03-11 08:11:11 -07:00
|
|
|
• virt_text_hide : hide the virtual text when
|
|
|
|
the background text is selected or hidden due
|
|
|
|
to horizontal scroll 'nowrap'
|
|
|
|
• hl_mode : control how highlights are combined
|
|
|
|
with the highlights of the text. Currently
|
|
|
|
only affects virt_text highlights, but might
|
|
|
|
affect`hl_group`in later versions.
|
|
|
|
• "replace": only show the virt_text color.
|
|
|
|
This is the default
|
|
|
|
• "combine": combine with background text
|
|
|
|
color
|
|
|
|
• "blend": blend with background text color.
|
|
|
|
|
2021-04-24 03:47:52 -07:00
|
|
|
• hl_eol : when true, for a multiline highlight
|
|
|
|
covering the EOL of a line, continue the
|
|
|
|
highlight for the rest of the screen line
|
|
|
|
(just like for diff and cursorline highlight).
|
2020-10-20 12:57:07 -07:00
|
|
|
• ephemeral : for use with
|
|
|
|
|nvim_set_decoration_provider| callbacks. The
|
|
|
|
mark will only be used for the current redraw
|
|
|
|
cycle, and not be permantently stored in the
|
|
|
|
buffer.
|
2021-01-23 11:31:01 -07:00
|
|
|
• right_gravity : boolean that indicates the
|
|
|
|
direction the extmark will be shifted in when
|
|
|
|
new text is inserted (true for right, false
|
|
|
|
for left). defaults to true.
|
|
|
|
• end_right_gravity : boolean that indicates the
|
|
|
|
direction the extmark end position (if it
|
|
|
|
exists) will be shifted in when new text is
|
|
|
|
inserted (true for right, false for left).
|
|
|
|
Defaults to false.
|
2021-04-06 05:22:33 -07:00
|
|
|
• priority: a priority value for the highlight
|
|
|
|
group. For example treesitter highlighting
|
|
|
|
uses a value of 100.
|
2019-11-09 04:41:50 -07:00
|
|
|
|
|
|
|
Return: ~
|
2019-11-25 02:08:02 -07:00
|
|
|
Id of the created/updated extmark
|
2019-11-09 04:41:50 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_set_keymap()*
|
|
|
|
nvim_buf_set_keymap({buffer}, {mode}, {lhs}, {rhs}, {opts})
|
|
|
|
Sets a buffer-local |mapping| for the given mode.
|
2019-11-09 04:41:50 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-11-25 02:08:02 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2019-11-09 04:41:50 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
See also: ~
|
|
|
|
|nvim_set_keymap()|
|
2019-11-09 04:41:50 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
*nvim_buf_set_lines()*
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
nvim_buf_set_lines({buffer}, {start}, {end}, {strict_indexing}, {replacement})
|
2019-12-28 04:27:25 -07:00
|
|
|
Sets (replaces) a line-range in the buffer.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Indexing is zero-based, end-exclusive. Negative indices are
|
|
|
|
interpreted as length+1+index: -1 refers to the index past the
|
|
|
|
end. So to change or delete the last element use start=-2 and
|
|
|
|
end=-1.
|
2017-11-05 18:00:39 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
To insert lines at a given index, set `start` and `end` to the
|
|
|
|
same index. To delete a range of lines, set `replacement` to
|
|
|
|
an empty array.
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Out-of-bounds indices are clamped to the nearest valid value,
|
|
|
|
unless `strict_indexing` is set.
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{start} First line index
|
|
|
|
{end} Last line index (exclusive)
|
|
|
|
{strict_indexing} Whether out-of-bounds should be an
|
|
|
|
error.
|
|
|
|
{replacement} Array of lines to use as replacement
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_set_name({buffer}, {name}) *nvim_buf_set_name()*
|
|
|
|
Sets the full file name for a buffer
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{name} Buffer name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_set_option({buffer}, {name}, {value}) *nvim_buf_set_option()*
|
|
|
|
Sets a buffer option value. Passing 'nil' as value deletes the
|
|
|
|
option (only works if there's a global fallback)
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{name} Option name
|
|
|
|
{value} Option value
|
|
|
|
|
2021-01-01 12:24:40 -07:00
|
|
|
*nvim_buf_set_text()*
|
|
|
|
nvim_buf_set_text({buffer}, {start_row}, {start_col}, {end_row}, {end_col},
|
|
|
|
{replacement})
|
|
|
|
Sets (replaces) a range in the buffer
|
|
|
|
|
|
|
|
This is recommended over nvim_buf_set_lines when only
|
|
|
|
modifying parts of a line, as extmarks will be preserved on
|
|
|
|
non-modified parts of the touched lines.
|
|
|
|
|
|
|
|
Indexing is zero-based and end-exclusive.
|
|
|
|
|
|
|
|
To insert text at a given index, set `start` and `end` ranges
|
|
|
|
to the same index. To delete a range, set `replacement` to an
|
|
|
|
array containing an empty string, or simply an empty array.
|
|
|
|
|
|
|
|
Prefer nvim_buf_set_lines when adding or deleting entire lines
|
|
|
|
only.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{start_row} First line index
|
|
|
|
{start_column} Last column
|
|
|
|
{end_row} Last line index
|
|
|
|
{end_column} Last column
|
|
|
|
{replacement} Array of lines to use as replacement
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_buf_set_var({buffer}, {name}, {value}) *nvim_buf_set_var()*
|
|
|
|
Sets a buffer-scoped (b:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
|
|
|
{name} Variable name
|
|
|
|
{value} Variable value
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-08-04 18:17:08 -07:00
|
|
|
*nvim_buf_set_virtual_text()*
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
nvim_buf_set_virtual_text({buffer}, {src_id}, {line}, {chunks}, {opts})
|
2018-08-04 18:17:08 -07:00
|
|
|
Set the virtual text (annotation) for a buffer line.
|
|
|
|
|
|
|
|
By default (and currently the only option) the text will be
|
|
|
|
placed after the buffer text. Virtual text will never cause
|
|
|
|
reflow, rather virtual text will be truncated at the end of
|
2019-01-26 12:10:59 -07:00
|
|
|
the screen line. The virtual text will begin one cell
|
|
|
|
(|lcs-eol| or space) after the ordinary text.
|
2018-08-04 18:17:08 -07:00
|
|
|
|
2018-11-15 18:00:04 -07:00
|
|
|
Namespaces are used to support batch deletion/updating of
|
|
|
|
virtual text. To create a namespace, use
|
2020-09-05 22:10:56 -07:00
|
|
|
|nvim_create_namespace()|. Virtual text is cleared using
|
|
|
|
|nvim_buf_clear_namespace()|. The same `ns_id` can be used for
|
2018-11-15 18:00:04 -07:00
|
|
|
both virtual text and highlights added by
|
2020-09-05 22:10:56 -07:00
|
|
|
|nvim_buf_add_highlight()|, both can then be cleared with a
|
|
|
|
single call to |nvim_buf_clear_namespace()|. If the virtual
|
|
|
|
text never will be cleared by an API call, pass `ns_id = -1` .
|
2018-11-15 18:00:04 -07:00
|
|
|
|
|
|
|
As a shorthand, `ns_id = 0` can be used to create a new
|
|
|
|
namespace for the virtual text, the allocated id is then
|
|
|
|
returned.
|
2018-11-04 19:50:22 -07:00
|
|
|
|
2018-08-04 18:17:08 -07:00
|
|
|
Parameters: ~
|
2019-03-03 07:01:16 -07:00
|
|
|
{buffer} Buffer handle, or 0 for current buffer
|
2018-11-15 18:00:04 -07:00
|
|
|
{ns_id} Namespace to use or 0 to create a namespace, or
|
2018-08-04 18:17:08 -07:00
|
|
|
-1 for a ungrouped annotation
|
2019-01-26 12:10:59 -07:00
|
|
|
{line} Line to annotate with virtual text
|
|
|
|
(zero-indexed)
|
2018-08-04 18:17:08 -07:00
|
|
|
{chunks} A list of [text, hl_group] arrays, each
|
|
|
|
representing a text chunk with specified
|
|
|
|
highlight. `hl_group` element can be omitted for
|
|
|
|
no highlight.
|
|
|
|
{opts} Optional parameters. Currently not used.
|
|
|
|
|
|
|
|
Return: ~
|
2018-11-15 18:00:04 -07:00
|
|
|
The ns_id that was used
|
2018-08-04 18:17:08 -07:00
|
|
|
|
2019-11-10 08:38:04 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
==============================================================================
|
|
|
|
Window Functions *api-window*
|
2019-11-10 08:38:04 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_close({window}, {force}) *nvim_win_close()*
|
|
|
|
Closes the window (like |:close| with a |window-ID|).
|
2019-11-10 08:38:04 -07:00
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-11-10 08:38:04 -07:00
|
|
|
Parameters: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{force} Behave like `:close!` The last window of a
|
|
|
|
buffer with unwritten changes can be closed. The
|
|
|
|
buffer will become hidden, even if 'hidden' is
|
|
|
|
not set.
|
2019-08-25 16:01:01 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_del_var({window}, {name}) *nvim_win_del_var()*
|
|
|
|
Removes a window-scoped (w:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{name} Variable name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_win_get_buf({window}) *nvim_win_get_buf()*
|
|
|
|
Gets the current buffer in a window
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Buffer handle
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_get_config({window}) *nvim_win_get_config()*
|
|
|
|
Gets window configuration.
|
|
|
|
|
|
|
|
The returned value may be given to |nvim_open_win()|.
|
|
|
|
|
|
|
|
`relative` is empty for normal windows.
|
2018-11-15 18:00:04 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2019-12-28 04:27:25 -07:00
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Map defining the window configuration, see
|
|
|
|
|nvim_open_win()|
|
2018-11-15 18:00:04 -07:00
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
nvim_win_get_cursor({window}) *nvim_win_get_cursor()*
|
2019-05-24 09:07:16 -07:00
|
|
|
Gets the (1,0)-indexed cursor position in the window.
|
|
|
|
|api-indexing|
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
(row, col) tuple
|
|
|
|
|
|
|
|
nvim_win_get_height({window}) *nvim_win_get_height()*
|
|
|
|
Gets the window height
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Height as a count of rows
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_get_number({window}) *nvim_win_get_number()*
|
|
|
|
Gets the window number
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Window number
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_win_get_option({window}, {name}) *nvim_win_get_option()*
|
|
|
|
Gets a window option value
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
{name} Option name
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Option value
|
|
|
|
|
|
|
|
nvim_win_get_position({window}) *nvim_win_get_position()*
|
|
|
|
Gets the window position in display cells. First position is
|
|
|
|
zero.
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
(row, col) tuple with the window position
|
|
|
|
|
|
|
|
nvim_win_get_tabpage({window}) *nvim_win_get_tabpage()*
|
|
|
|
Gets the window tabpage
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Tabpage that contains the window
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_get_var({window}, {name}) *nvim_win_get_var()*
|
|
|
|
Gets a window-scoped (w:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Variable value
|
|
|
|
|
|
|
|
nvim_win_get_width({window}) *nvim_win_get_width()*
|
|
|
|
Gets the window width
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
|
|
|
|
Return: ~
|
|
|
|
Width as a count of columns
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2021-03-15 23:02:20 -07:00
|
|
|
nvim_win_hide({window}) *nvim_win_hide()*
|
|
|
|
Closes the window and hide the buffer it contains (like
|
|
|
|
|:hide| with a |window-ID|).
|
|
|
|
|
|
|
|
Like |:hide| the buffer becomes hidden unless another window
|
|
|
|
is editing it, or 'bufhidden' is `unload` , `delete` or `wipe`
|
|
|
|
as opposed to |:close| or |nvim_win_close|, which will close
|
|
|
|
the buffer.
|
|
|
|
|
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
nvim_win_is_valid({window}) *nvim_win_is_valid()*
|
|
|
|
Checks if a window is valid
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
true if the window is valid, false otherwise
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_set_buf({window}, {buffer}) *nvim_win_set_buf()*
|
|
|
|
Sets the current buffer in a window, without side-effects
|
|
|
|
|
2020-11-24 05:37:29 -07:00
|
|
|
Attributes: ~
|
|
|
|
not allowed when |textlock| is active
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{buffer} Buffer handle
|
|
|
|
|
2019-03-16 05:57:50 -07:00
|
|
|
nvim_win_set_config({window}, {config}) *nvim_win_set_config()*
|
2019-09-09 15:35:30 -07:00
|
|
|
Configures window layout. Currently only for floating and
|
|
|
|
external windows (including changing a split window to those
|
|
|
|
layouts).
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
When reconfiguring a floating window, absent option keys will
|
2019-09-09 15:35:30 -07:00
|
|
|
not be changed. `row` / `col` and `relative` must be
|
|
|
|
reconfigured together.
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2019-03-15 10:18:56 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2019-09-09 15:35:30 -07:00
|
|
|
{config} Map defining the window configuration, see
|
|
|
|
|nvim_open_win()|
|
|
|
|
|
|
|
|
See also: ~
|
|
|
|
|nvim_open_win()|
|
2019-03-15 10:18:56 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_set_cursor({window}, {pos}) *nvim_win_set_cursor()*
|
|
|
|
Sets the (1,0)-indexed cursor position in the window.
|
|
|
|
|api-indexing|
|
2019-03-15 10:18:56 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{pos} (row, col) tuple representing the new position
|
2019-03-15 10:18:56 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_set_height({window}, {height}) *nvim_win_set_height()*
|
|
|
|
Sets the window height. This will only succeed if the screen
|
|
|
|
is split horizontally.
|
2019-03-15 10:18:56 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2019-12-28 04:27:25 -07:00
|
|
|
{height} Height as a count of rows
|
2019-03-15 10:18:56 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_win_set_option({window}, {name}, {value}) *nvim_win_set_option()*
|
|
|
|
Sets a window option value. Passing 'nil' as value deletes the
|
|
|
|
option(only works if there's a global fallback)
|
2019-03-15 10:18:56 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{name} Option name
|
|
|
|
{value} Option value
|
|
|
|
|
|
|
|
nvim_win_set_var({window}, {name}, {value}) *nvim_win_set_var()*
|
|
|
|
Sets a window-scoped (w:) variable
|
2019-03-12 05:46:02 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{window} Window handle, or 0 for current window
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
|
|
|
{value} Variable value
|
|
|
|
|
|
|
|
nvim_win_set_width({window}, {width}) *nvim_win_set_width()*
|
|
|
|
Sets the window width. This will only succeed if the screen is
|
|
|
|
split vertically.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{window} Window handle, or 0 for current window
|
|
|
|
{width} Width as a count of columns
|
2019-03-12 05:46:02 -07:00
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
==============================================================================
|
|
|
|
Tabpage Functions *api-tabpage*
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_tabpage_del_var({tabpage}, {name}) *nvim_tabpage_del_var()*
|
|
|
|
Removes a tab-scoped (t:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2019-12-28 04:27:25 -07:00
|
|
|
{name} Variable name
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_tabpage_get_number({tabpage}) *nvim_tabpage_get_number()*
|
|
|
|
Gets the tabpage number
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
Tabpage number
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_tabpage_get_var({tabpage}, {name}) *nvim_tabpage_get_var()*
|
|
|
|
Gets a tab-scoped (t:) variable
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
{name} Variable name
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
Return: ~
|
|
|
|
Variable value
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_tabpage_get_win({tabpage}) *nvim_tabpage_get_win()*
|
|
|
|
Gets the current window in a tabpage
|
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2017-03-01 09:18:03 -07:00
|
|
|
Window handle
|
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_tabpage_is_valid({tabpage}) *nvim_tabpage_is_valid()*
|
|
|
|
Checks if a tabpage is valid
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
true if the tabpage is valid, false otherwise
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2019-12-28 04:27:25 -07:00
|
|
|
nvim_tabpage_list_wins({tabpage}) *nvim_tabpage_list_wins()*
|
|
|
|
Gets the windows in a tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Parameters: ~
|
2019-08-25 16:01:01 -07:00
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
2017-03-01 09:18:03 -07:00
|
|
|
|
2018-06-29 10:27:50 -07:00
|
|
|
Return: ~
|
2019-12-28 04:27:25 -07:00
|
|
|
List of windows in `tabpage`
|
|
|
|
|
2019-12-31 07:52:14 -07:00
|
|
|
*nvim_tabpage_set_var()*
|
|
|
|
nvim_tabpage_set_var({tabpage}, {name}, {value})
|
2019-12-28 04:27:25 -07:00
|
|
|
Sets a tab-scoped (t:) variable
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{tabpage} Tabpage handle, or 0 for current tabpage
|
|
|
|
{name} Variable name
|
|
|
|
{value} Variable value
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
|
|
|
|
==============================================================================
|
|
|
|
UI Functions *api-ui*
|
|
|
|
|
|
|
|
nvim_ui_attach({width}, {height}, {options}) *nvim_ui_attach()*
|
2019-04-08 18:14:27 -07:00
|
|
|
Activates UI events on the channel.
|
|
|
|
|
|
|
|
Entry point of all UI clients. Allows |--embed| to continue
|
|
|
|
startup. Implies that the client is ready to show the UI. Adds
|
|
|
|
the client to the list of UIs. |nvim_list_uis()|
|
|
|
|
|
|
|
|
Note:
|
|
|
|
If multiple UI clients are attached, the global screen
|
|
|
|
dimensions degrade to the smallest client. E.g. if client
|
|
|
|
A requests 80x40 but client B requests 200x100, the global
|
|
|
|
screen has size 80x40.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{width} Requested screen columns
|
|
|
|
{height} Requested screen rows
|
2019-05-11 07:58:47 -07:00
|
|
|
{options} |ui-option| map
|
2017-03-01 09:18:03 -07:00
|
|
|
|
|
|
|
nvim_ui_detach() *nvim_ui_detach()*
|
2019-04-08 18:14:27 -07:00
|
|
|
Deactivates UI events on the channel.
|
|
|
|
|
|
|
|
Removes the client from the list of UIs. |nvim_list_uis()|
|
|
|
|
|
2020-02-24 01:40:58 -07:00
|
|
|
*nvim_ui_pum_set_bounds()*
|
|
|
|
nvim_ui_pum_set_bounds({width}, {height}, {row}, {col})
|
2020-07-02 04:09:17 -07:00
|
|
|
Tells Nvim the geometry of the popumenu, to align floating
|
|
|
|
windows with an external popup menu.
|
2020-02-24 01:40:58 -07:00
|
|
|
|
2020-07-02 04:09:17 -07:00
|
|
|
Note that this method is not to be confused with
|
|
|
|
|nvim_ui_pum_set_height()|, which sets the number of visible
|
|
|
|
items in the popup menu, while this function sets the bounding
|
lsp: vim.lsp.diagnostic (#12655)
Breaking Changes:
- Deprecated all `vim.lsp.util.{*diagnostics*}()` functions.
- Instead, all functions must be found in vim.lsp.diagnostic
- For now, they issue a warning ONCE per neovim session. In a
"little while" we will remove them completely.
- `vim.lsp.callbacks` has moved to `vim.lsp.handlers`.
- For a "little while" we will just redirect `vim.lsp.callbacks` to
`vim.lsp.handlers`. However, we will remove this at some point, so
it is recommended that you change all of your references to
`callbacks` into `handlers`.
- This also means that for functions like |vim.lsp.start_client()|
and similar, keyword style arguments have moved from "callbacks"
to "handlers". Once again, these are currently being forward, but
will cease to be forwarded in a "little while".
- Changed the highlight groups for LspDiagnostic highlight as they were
inconsistently named.
- For more information, see |lsp-highlight-diagnostics|
- Changed the sign group names as well, to be consistent with
|lsp-highlight-diagnostics|
General Enhancements:
- Rewrote much of the getting started help document for lsp. It also
provides a much nicer configuration strategy, so as to not recommend
globally overwriting builtin neovim mappings.
LSP Enhancements:
- Introduced the concept of |lsp-handlers| which will allow much better
customization for users without having to copy & paste entire files /
functions / etc.
Diagnostic Enhancements:
- "goto next diagnostic" |vim.lsp.diagnostic.goto_next()|
- "goto prev diagnostic" |vim.lsp.diagnostic.goto_prev()|
- For each of the gotos, auto open diagnostics is available as a
configuration option
- Configurable diagnostic handling:
- See |vim.lsp.diagnostic.on_publish_diagnostics()|
- Delay display until after insert mode
- Configure signs
- Configure virtual text
- Configure underline
- Set the location list with the buffers diagnostics.
- See |vim.lsp.diagnostic.set_loclist()|
- Better performance for getting counts and line diagnostics
- They are now cached on save, to enhance lookups.
- Particularly useful for checking in statusline, etc.
- Actual testing :)
- See ./test/functional/plugin/lsp/diagnostic_spec.lua
- Added `guisp` for underline highlighting
NOTE: "a little while" means enough time to feel like most plugins and
plugin authors have had a chance to refactor their code to use the
updated calls. Then we will remove them completely. There is no need to
keep them, because we don't have any released version of neovim that
exposes these APIs. I'm trying to be nice to people following HEAD :)
Co-authored: [Twitch Chat 2020](https://twitch.tv/teej_dv)
2020-11-12 20:21:34 -07:00
|
|
|
box of the popup menu, including visual elements such as
|
|
|
|
borders and sliders. Floats need not use the same font size,
|
2020-07-02 04:09:17 -07:00
|
|
|
nor be anchored to exact grid corners, so one can set
|
|
|
|
floating-point numbers to the popup menu geometry.
|
2020-02-24 01:40:58 -07:00
|
|
|
|
|
|
|
Parameters: ~
|
2020-03-03 02:43:02 -07:00
|
|
|
{width} Popupmenu width.
|
|
|
|
{height} Popupmenu height.
|
|
|
|
{row} Popupmenu row.
|
2020-07-02 04:09:17 -07:00
|
|
|
{col} Popupmenu height.
|
|
|
|
|
|
|
|
nvim_ui_pum_set_height({height}) *nvim_ui_pum_set_height()*
|
|
|
|
Tells Nvim the number of elements displaying in the popumenu,
|
|
|
|
to decide <PageUp> and <PageDown> movement.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{height} Popupmenu height, must be greater than zero.
|
2020-02-24 01:40:58 -07:00
|
|
|
|
2017-03-01 09:18:03 -07:00
|
|
|
nvim_ui_set_option({name}, {value}) *nvim_ui_set_option()*
|
2019-12-28 04:27:25 -07:00
|
|
|
TODO: Documentation
|
|
|
|
|
|
|
|
nvim_ui_try_resize({width}, {height}) *nvim_ui_try_resize()*
|
2017-03-01 09:18:03 -07:00
|
|
|
TODO: Documentation
|
|
|
|
|
2019-01-10 17:20:15 -07:00
|
|
|
*nvim_ui_try_resize_grid()*
|
|
|
|
nvim_ui_try_resize_grid({grid}, {width}, {height})
|
|
|
|
Tell Nvim to resize a grid. Triggers a grid_resize event with
|
|
|
|
the requested grid size or the maximum size if it exceeds size
|
|
|
|
limits.
|
|
|
|
|
|
|
|
On invalid grid handle, fails with error.
|
|
|
|
|
|
|
|
Parameters: ~
|
|
|
|
{grid} The handle of the grid to be changed.
|
|
|
|
{width} The new requested width.
|
|
|
|
{height} The new requested height.
|
|
|
|
|
2017-12-16 13:33:59 -07:00
|
|
|
vim:tw=78:ts=8:ft=help:norl:
|