rneovim.git/test/functional/core, branch floattitle Neovim fork with Rahm's personal hacks. fix: find multibyte file name in line (#20519) 2022-10-07T01:43:16+00:00 zeertzjq zeertzjq@outlook.com 2022-10-07T01:43:16+00:00 cfdb4cbada8c65aa57e69776bcc0f7b8b298317a And remove unnecessary unsigned casts in fold marker comparison. 
And remove unnecessary unsigned casts in fold marker comparison.
 feat(messages)!: graduate the 'msgsep' feature 2022-10-05T18:12:59+00:00 bfredl bjorn.linse@gmail.com 2022-09-27T14:19:15+00:00 6ae144a92171cf9ae52bddddc3a081a4efaabe9f The old behaviour (e.g. via `set display-=msgsep`) will not be available. Assuming that messages always are being drawn on msg_grid (or not drawn at all, and forwarded to `ext_messages` enabled UI) will allows some simplifcations and enhancements moving forward. 
The old behaviour (e.g. via `set display-=msgsep`) will not be available.
Assuming that messages always are being drawn on msg_grid
(or not drawn at all, and forwarded to `ext_messages` enabled UI)
will allows some simplifcations and enhancements moving forward.
feat(gen_help_html.lua): adapt to new parser 2022-09-28T16:34:20+00:00 Justin M. Keyes justinkz@gmail.com 2022-09-25T00:20:47+00:00 16336c486ecb5a60e85a870904316308c7d7fc3f - adapt to parser changes from https://github.com/vigoux/tree-sitter-vimdoc/pull/16 - numerous other generator improvements 
- adapt to parser changes from https://github.com/vigoux/tree-sitter-vimdoc/pull/16
- numerous other generator improvements
feat: ":write!" skips "file changed" warning #18665 2022-09-25T01:57:10+00:00 Louis Sven Goulet 31444858+lorlouis@users.noreply.github.com 2022-09-25T01:57:10+00:00 2a3cb0893b03aeff4d8c0b2116cbddda53bba5a2 Problem: Cannot opt-out of "WARNING: The file has been changed since reading it!!!", even with ":write!". Solution: Change ":write!" to skip the warning. closes #7270 
Problem:
Cannot opt-out of "WARNING: The file has been changed since reading
it!!!", even with ":write!".

Solution:
Change ":write!" to skip the warning.

closes #7270
 test(remote_spec): reduce flakiness in waiting for client exit (#20230) 2022-09-17T08:17:51+00:00 zeertzjq zeertzjq@outlook.com 2022-09-17T08:17:51+00:00 3c3f3e7353ba2cb9071183cd05036ca2a98d3672 It is less likely for client to exit between jobstart() and jobwait() if they are invoked in the same RPC request instead of two separate ones. 
It is less likely for client to exit between jobstart() and jobwait() if
they are invoked in the same RPC request instead of two separate ones.
 ci: move BSD jobs from sourcehut to Cirrus CI #19616 2022-09-08T22:12:42+00:00 dundargoc 33953936+dundargoc@users.noreply.github.com 2022-09-08T22:12:42+00:00 2d6735d8cecc587eb5549f65260ee9ddeb8e1d78 dispatch.sr.ht is being deprecated, meaning that using sourcehut CI won't be possible (see https://github.com/neovim/neovim/issues/19609). Since Github Actions doesn't provide any BSD runners an external service is required and Cirrus CI seems like a good replacement for sourcehut. Initially experimented with using FreeBSD and OpenBSD virtual machines in GitHub Actions, but Cirrus has been a much better fit with better performance, logs and overall experience. Failing tests are automatically skipped on FreeBSD regardless if it's on CI or not. Ideally these tests should only be skipped in CI with the help of `isCI` helper function. Unfortunately, the tests don't recognize the environment variable CIRRUS_CI even if it's set manually. This workaround is good enough for the time being, but we might want to only skip tests when using the CI (or even better, fix the failing tests). Closes: https://github.com/neovim/neovim/issues/19609 
dispatch.sr.ht is being deprecated, meaning that using sourcehut CI
won't be possible (see https://github.com/neovim/neovim/issues/19609).
Since Github Actions doesn't provide any BSD runners an external service
is required and Cirrus CI seems like a good replacement for sourcehut.

Initially experimented with using FreeBSD and OpenBSD virtual machines
in GitHub Actions, but Cirrus has been a much better fit with better
performance, logs and overall experience.

Failing tests are automatically skipped on FreeBSD regardless if it's on
CI or not. Ideally these tests should only be skipped in CI with the
help of `isCI` helper function. Unfortunately, the tests don't recognize
the environment variable CIRRUS_CI even if it's set manually. This
workaround is good enough for the time being, but we might want to only
skip tests when using the CI (or even better, fix the failing tests).

Closes: https://github.com/neovim/neovim/issues/19609
 revert: "jobstart(): Fix hang on non-executable cwd #9204" (#19826) 2022-08-18T14:09:50+00:00 zeertzjq zeertzjq@outlook.com 2022-08-18T14:09:50+00:00 36f0b508c548ba7a6fe916be6c673c4a4738f246 This reverts commit c4c74c3883aa3122c0c877ca8dd7b26beb5cc4aa. LibUV already gives an error for this, so this isn't needed. 
This reverts commit c4c74c3883aa3122c0c877ca8dd7b26beb5cc4aa.

LibUV already gives an error for this, so this isn't needed.
 vim-patch:7.4.1168 (#19645) 2022-08-13T13:31:00+00:00 zeertzjq zeertzjq@outlook.com 2022-08-13T13:31:00+00:00 02a4974418b7fb18c5034b7b2fc85ce4cde7d370 Problem: This doesn't give the right result: eval(string(v:true)). (Nikolay Pavlov) Solution: Make the string "v:true" instead of "true". https://github.com/vim/vim/commit/f48aa160fdd7b8caa7678e1a2139244dd2bdc547 
Problem:    This doesn't give the right result: eval(string(v:true)). (Nikolay
            Pavlov)
Solution:   Make the string "v:true" instead of "true".
https://github.com/vim/vim/commit/f48aa160fdd7b8caa7678e1a2139244dd2bdc547
 test: make Ex mode exit test test what it wants to test (#19728) 2022-08-12T01:04:08+00:00 zeertzjq zeertzjq@outlook.com 2022-08-12T01:04:08+00:00 0d9e09bf670724caec9939a7165e25c4abc40291 






vim-patch:8.2.1281: the "trailing characters" error can be hard to understand
2022-08-07T06:39:19+00:00

zeertzjq
zeertzjq@outlook.com

2022-08-07T06:09:32+00:00

48051ed62cde6ab572bcd48768fe43740f3cd48c

Problem:    The "trailing characters" error can be hard to understand.
Solution:   Add the trailing characters to the message.
https://github.com/vim/vim/commit/2d06bfde29bd3a62fc85823d2aa719ef943bd319





Problem:    The "trailing characters" error can be hard to understand.
Solution:   Add the trailing characters to the message.
https://github.com/vim/vim/commit/2d06bfde29bd3a62fc85823d2aa719ef943bd319