rneovim.git/src/nvim/api, branch v0.1.3

api/buffer: deprecate old line and line slice functions

2016-04-01T09:30:00+00:00

api/buffer: introduce buffer_[gs]et_lines with new indexing convention.

2016-04-01T09:29:51+00:00

-1 is index past the end, and -2 is the index of the last element.
This eliminates the need for include_start/include_end.

Allow the handling of out-of-bounds to be configurable.

bufhl: new mechanism for plugins to add highlights to a buffer

2016-02-23T20:29:01+00:00

Remove unnecessary includes for errno.h

2015-11-25T21:38:33+00:00

shada: Refactor history merger to use statically sized 2linked list

2015-10-08T19:00:10+00:00

Also fixes the error: when writing shada files existing history items may be
freed.

Warning: valgrind reports some memory leaks.

viminfo: First version of ShaDa file dumping

2015-10-08T18:59:51+00:00

What works:

1. ShaDa file dumping: header, registers, jump list, history, search patterns,
   substitute strings, variables.
2. ShaDa file reading: registers, global marks, variables.

Most was not tested.

TODO:

1. Merging.
2. Reading history, local marks, jump and buffer lists.
3. Documentation update.
4. Converting some data from &encoding.
5. Safer variant of dumping viminfo (dump to temporary file then rename).
6. Removing old viminfo code (currently masked with `#if 0` in a ShaDa file for
   reference).

Fix append() without line argument

2015-09-20T10:38:41+00:00

We want to switch include_start/end when the index is positive or
negative.

api: vim_err_write: don't wait for return in the middle of a message

2015-09-16T19:42:57+00:00

api: buffer_insert: fix bounds. #3315

2015-09-09T04:35:52+00:00

buffer_insert calls buffer_set_line_slice excluding the start
line number and including the end, but it should be the opposite.

Closes https://github.com/neovim/neovim/issues/3212
Closes https://github.com/neovim/python-client/issues/103

msgpack: Replace FUNC_ATTR_DEFERRED by FUNC_ATTR_ASYNC

2015-08-13T10:41:04+00:00

API functions exposed via msgpack-rpc now fall into two categories:

- async functions, which are executed as soon as the request is parsed
- sync functions, which are invoked in nvim main loop when processing the
  `K_EVENT special key

Only a few functions which can be safely executed in any context are marked as
async.