rneovim.git/test/functional/lua/buffer_updates_spec.lua, branch fix_repeatcmdline Neovim fork with Rahm's personal hacks. fix: invoke changed_bytes when rewriting <Tab> char #25125 2023-09-15T10:45:51+00:00 Ilia Choly ilia.choly@gmail.com 2023-09-15T10:45:51+00:00 f5a09f1b035254f6ee773a1f88f79ab5913b48a0 When tabstop and shiftwidth are not equal, tabs are inserted as individual spaces and then rewritten as tab characters in a second pass. That second pass did not call changed_bytes which resulted in events being omitted. Fixes #25092 
When tabstop and shiftwidth are not equal, tabs are inserted as individual
spaces and then rewritten as tab characters in a second pass. That second pass
did not call changed_bytes which resulted in events being omitted.

Fixes #25092
 fix(spell): splice extmarks on :spellrepall (#23929) 2023-06-06T02:32:30+00:00 zeertzjq zeertzjq@outlook.com 2023-06-06T02:32:30+00:00 eceb2dffce3908507092ffe425b1ceef5baeb1ab 






test: don't unnecessarily specify win/buf for `nvim_(get|set)_option_value`
2023-05-22T07:02:07+00:00

Famiu Haque
famiuhaque@proton.me

2023-05-22T06:47:10+00:00

576dddb46168e81aa0f78c28816082c662dedea1

`nvim_(get|set)_option_value` pick the current buffer / window by default for buffer-local/window-local (but not global-local) options. So specifying `buf = 0` or `win = 0` in opts is unnecessary for those options. This PR removes those to reduce code clutter.





`nvim_(get|set)_option_value` pick the current buffer / window by default for buffer-local/window-local (but not global-local) options. So specifying `buf = 0` or `win = 0` in opts is unnecessary for those options. This PR removes those to reduce code clutter.







refactor(options): deprecate nvim[_buf|_win]_[gs]et_option
2023-05-21T09:14:01+00:00

Lewis Russell
lewis6991@gmail.com

2022-12-19T16:37:45+00:00

1fe1bb084d0099fc4f9bfdc11189485d0f74b75a

Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Co-authored-by: famiu <famiuhaque@protonmail.com>





Co-authored-by: zeertzjq <zeertzjq@outlook.com>
Co-authored-by: famiu <famiuhaque@protonmail.com>







test: replace lfs with luv and vim.fs
2023-04-04T19:59:06+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2023-04-04T19:59:06+00:00

743860de40502227b3f0ed64317eb937d24d4a36

test: replace lfs with luv

luv already pretty much does everything lfs does, so this duplication
of dependencies isn't needed.




test: replace lfs with luv

luv already pretty much does everything lfs does, so this duplication
of dependencies isn't needed.






fix(diff): trigger on_bytes only once after diffget/diffput
2023-03-11T09:22:00+00:00

Jaehwang Jung
tomtomjhj@gmail.com

2023-03-11T07:52:46+00:00

2748202e0eb28574cdc65dcb758adea89023271d

Problem: The fix from b50ee4a8dc4306e4be78ac33fb74b21dc6be5538 may
adjust extmark twice, triggering on_bytes callback twice.

Solution: Don't let mark_adjust adjust extmark.





Problem: The fix from b50ee4a8dc4306e4be78ac33fb74b21dc6be5538 may
adjust extmark twice, triggering on_bytes callback twice.

Solution: Don't let mark_adjust adjust extmark.







fix(buffer_updates): save and restore current window cursor (#16732)
2023-03-09T02:19:00+00:00

zeertzjq
zeertzjq@outlook.com

2023-03-09T02:19:00+00:00

89a525de9f2551e460cc91d40fd7afbb7e07622f

When a buffer update callback is called, textlock is active so buffer
text cannot be changed, but cursor can still be moved. This can cause
problems when the buffer update is in the middle of an operator, like
the one mentioned in #16729. The solution is to save cursor position and
restore it afterwards, like how cursor is saved and restored when
evaluating an <expr> mapping.




When a buffer update callback is called, textlock is active so buffer
text cannot be changed, but cursor can still be moved. This can cause
problems when the buffer update is in the middle of an operator, like
the one mentioned in #16729. The solution is to save cursor position and
restore it afterwards, like how cursor is saved and restored when
evaluating an <expr> mapping.






docs: fix typos (#20394)
2022-09-30T07:53:52+00:00

dundargoc
33953936+dundargoc@users.noreply.github.com

2022-09-30T07:53:52+00:00

df646572c53f55268a5dbb61628d7c3b302d5663

Co-authored-by: Raphael <glephunter@gmail.com>
Co-authored-by: smjonas <jonas.strittmatter@gmx.de>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>




Co-authored-by: Raphael <glephunter@gmail.com>
Co-authored-by: smjonas <jonas.strittmatter@gmx.de>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>






fix!: make :undo! notify buffer update callbacks (#20344)
2022-09-25T23:15:07+00:00

zeertzjq
zeertzjq@outlook.com

2022-09-25T23:15:07+00:00

ac66f5af06ac1f306b0ddb366ba81093508546c4

When :undo! was introduced to Nvim the implementation of 'inccommand'
preview callback hasn't been fully decided yet, so not notifying buffer
update callbacks made sense for 'inccommand' preview callback in case it
needs to undo the changes itself.
Now it turns out that the undo-and-forget is done automatically for
'inccommand', so it doesn't make sense for :undo! to avoid notifying
buffer update callbacks anymore.




When :undo! was introduced to Nvim the implementation of 'inccommand'
preview callback hasn't been fully decided yet, so not notifying buffer
update callbacks made sense for 'inccommand' preview callback in case it
needs to undo the changes itself.
Now it turns out that the undo-and-forget is done automatically for
'inccommand', so it doesn't make sense for :undo! to avoid notifying
buffer update callbacks anymore.






Merge pull request #18931 from zeertzjq/regexp-num-escaped
2022-06-12T23:18:38+00:00

zeertzjq
zeertzjq@outlook.com

2022-06-12T23:18:38+00:00

c665773897ca31c6e1270c2d52939e33df35106b

fix(substitute): subtract number of backslashes later




fix(substitute): subtract number of backslashes later