rneovim.git/test/functional/editor, branch 20231130_mix Neovim fork with Rahm's personal hacks. fix(extmark): restore extmarks when completing original text 2023-11-29T22:38:27+00:00 Luuk van Baal luukvbaal@gmail.com 2023-05-22T14:57:30+00:00 8e97edb93f01a08b332289405f83624cfb067fcc 






vim-patch:9.0.2133: Cannot detect overstrike mode in Cmdline mode (#26263)
2023-11-28T03:46:20+00:00

zeertzjq
zeertzjq@outlook.com

2023-11-28T03:46:20+00:00

e6d38c7dac2e079d9b0f1621fef193bca858664f

Problem:  Cannot detect overstrike mode in Cmdline mode
Solution: Make mode() return "cr" for overstrike

closes: vim/vim#13569

https://github.com/vim/vim/commit/d1c3ef1f47c87d1da056c56564e1985fe6f2931d




Problem:  Cannot detect overstrike mode in Cmdline mode
Solution: Make mode() return "cr" for overstrike

closes: vim/vim#13569

https://github.com/vim/vim/commit/d1c3ef1f47c87d1da056c56564e1985fe6f2931d






fix(completion): filter results with complete+=f (#26029)
2023-11-18T04:26:52+00:00

Raphael
glephunter@gmail.com

2023-11-18T04:26:52+00:00

cdc8bacc7945da816738e330555fa85d3ffffd56












fix(completion): make sure the buffer name is valid (#25975)
2023-11-10T22:41:10+00:00

mortezadadgar
mortezadadgar97@gmail.com

2023-11-10T22:41:10+00:00

d1b2a5cf5fa583b556457d34a46ce7b940913a66

Problem:
crash from
  set complete+=f
  open a empty buffer
  C-N

Solution:
make sure the buffer name is valid.

regression from ae4ca4edf89ece433b61e8bf92c412298b58d9ea




Problem:
crash from
  set complete+=f
  open a empty buffer
  C-N

Solution:
make sure the buffer name is valid.

regression from ae4ca4edf89ece433b61e8bf92c412298b58d9ea






fix(marks): handle switching buffer properly (#25763)
2023-10-24T08:10:36+00:00

zeertzjq
zeertzjq@outlook.com

2023-10-24T08:10:36+00:00

d432bba4e46cf215a1879cdbe7673160e612425a












feat(complete): support f flag for complete buffer part
2023-10-21T12:06:36+00:00

glepnir
glephunter@gmail.com

2023-10-13T06:49:01+00:00

ae4ca4edf89ece433b61e8bf92c412298b58d9ea












fix(grid): add start column when getting char on line (#25627)
2023-10-13T13:43:06+00:00

zeertzjq
zeertzjq@outlook.com

2023-10-13T13:43:06+00:00

9f32deba56ea867a8bb9b9ab7f44bcc5142e8bbc












feat(completion): support completing more string options
2023-10-01T12:00:23+00:00

zeertzjq
zeertzjq@outlook.com

2023-10-01T11:07:16+00:00

01c51a491330bd10202c73aff92c0978984c0692












vim-patch:8.2.3517: TextChanged does not trigger after TextChangedI (#25384)
2023-09-27T10:51:40+00:00

zeertzjq
zeertzjq@outlook.com

2023-09-27T10:51:40+00:00

b65f4151d9e52a8521c0682a817c4dab9690e1e7

Problem:    TextChanged does not trigger after TextChangedI.
Solution:   Store the tick separately for TextChangedI. (Christian Brabandt,
            closes vim/vim#8968, closes vim/vim#8932)

https://github.com/vim/vim/commit/db3b44640d69ab27270691a3cab8d83cc93a0861

Co-authored-by: Christian Brabandt <cb@256bit.org>




Problem:    TextChanged does not trigger after TextChangedI.
Solution:   Store the tick separately for TextChangedI. (Christian Brabandt,
            closes vim/vim#8968, closes vim/vim#8932)

https://github.com/vim/vim/commit/db3b44640d69ab27270691a3cab8d83cc93a0861

Co-authored-by: Christian Brabandt <cb@256bit.org>






fix(folds): update folds in Insert mode with fdm=indent (#24402)
2023-07-21T00:56:08+00:00

Brandon Simmons
34775764+simmsbra@users.noreply.github.com

2023-07-21T00:56:08+00:00

58f94861442d182e153ba56b63b5b9845b295d2f

Previously, when using foldmethod=indent, inserting an unindented line
would inadvertently open closed folds below it.
As a performance improvement, folds were only updated once, across all
lines, after Insert mode was exited.

Now, the performance improvement is no longer being used when
foldmethod=indent, so folds are updated multiple times during Insert
mode, but only across the lines that are changing, which preserves the
folds (and their open/close states) instead of recreating them.




Previously, when using foldmethod=indent, inserting an unindented line
would inadvertently open closed folds below it.
As a performance improvement, folds were only updated once, across all
lines, after Insert mode was exited.

Now, the performance improvement is no longer being used when
foldmethod=indent, so folds are updated multiple times during Insert
mode, but only across the lines that are changing, which preserves the
folds (and their open/close states) instead of recreating them.