rneovim.git/test/functional/api/buffer_spec.lua, branch fix_repeatcmdline

fix(api): load buffer first on nvim_buf_set_lines (#25823)

2023-10-29T07:44:52+00:00

Fix #22670
Fix #8659

fix(api): more intuitive cursor updates in nvim_buf_set_text

2023-09-11T04:16:03+00:00

Fixes #22526

fix(api): nvim_buf_get_offset in a new buffer with zero or one lines

2023-08-30T10:01:35+00:00

fixes #24930

fix(api): better topline adjustments in nvim_buf_set_lines

2023-08-29T07:26:15+00:00

Some more reasonable defaults for topline:
  - if topline was replaced with another line, that now becomes topline
  - if line was inserted just before topline, display it. This is more
    similar to the previous API behavior.

fix(api): handle clearing out last line of non-current buffer

2023-08-28T10:39:02+00:00

fixes #24911

fix(undo): fix crash caused by checking undolevels in wrong buffer

2023-08-27T10:08:11+00:00

fixes #24894

fix(api): fix inconsistent behavior of topline touched in recent refactor

2023-08-27T10:07:46+00:00

The change in #24824 0081549 was not a regression, however it was an
incomplete change. Unfortunately some common plugins come to depend on
this exising self-inconsistent behavior. These plugins are going to need
to update for 0.10

nvim_buf_set_lines used to NOT adjust the topline correctly if a buffer
was displayed in just one window. However, if displayed in multiple
windows, it was correctly adjusted for any window not deemed the
current window for the buffer (which could be an arbitrary choice if the
buffer was not already current, as noted in the last rafactor)

This fixes so that all windows have their topline adjusted. The added
tests show this behavior, which should be the reasonable one.

refactor(change): do API changes to buffer without curbuf switch

2023-08-26T10:02:05+00:00

Most of the messy things when changing a non-current buffer is
not about the buffer, it is about windows. In particular, it is about
`curwin`.

When editing a non-current buffer which is displayed in some other
window in the current tabpage, one such window will be "borrowed" as the
curwin. But this means if two or more non-current windows displayed the buffers,
one of them will be treated differenty. this is not desirable.

In particular, with nvim_buf_set_text, cursor _column_ position was only
corrected for one single window. Two new tests are added: the test
with just one non-current window passes, but the one with two didn't.

Two corresponding such tests were also added for nvim_buf_set_lines.
This already worked correctly on master, but make sure this is
well-tested for future refactors.

Also, nvim_create_buf no longer invokes autocmds just because you happened
to use `scratch=true`. No option value was changed, therefore OptionSet
must not be fired.

fix(api): allow negative column arguments for nvim_buf_set_text (#23501)

2023-07-04T14:07:55+00:00

refactor(defaults): do not use C specific default values for options (#22500)

2023-06-06T16:26:29+00:00

The options 'path', 'include', and 'define' all use C-specific default
values. This may have made sense a long time ago when Vim was mostly
used just for writing C, but this is no longer the case, and we have
ample support for filetype specific configuration. Make the default
values of these options empty and move the C-specific values into a
filetype plugin where they belong.

Co-authored-by: zeertzjq