rneovim.git/src/nvim/os, branch userregs_2 Neovim fork with Rahm's personal hacks. fix(events): crash on SIGTSTP (Ctrl-Z) #33258 2025-04-02T15:12:19+00:00 phanium 91544758+phanen@users.noreply.github.com 2025-04-02T15:12:19+00:00 0b61bc8982304c3b8afd9f3c310b112227302bc5 Problem: Nvim crashes on receive SIGTSTP (Ctrl-Z) since 4dabeff308222307ede8e74a2bd341713a7f7d81. Solution: * Don't exit on SIGTSTP (not a deadly signal). * Avoid SIGTSTP handler in os/signal.c. Co-authored-by: 27Onion Nebell <zzy20080201@gmail.com> 
Problem:
Nvim crashes on receive SIGTSTP (Ctrl-Z) since 4dabeff308222307ede8e74a2bd341713a7f7d81.

Solution:
* Don't exit on SIGTSTP (not a deadly signal).
* Avoid SIGTSTP handler in os/signal.c.

Co-authored-by: 27Onion Nebell <zzy20080201@gmail.com>
 feat(editor): 'autowriteall' on SIGHUP/SIGQUIT #32843 2025-03-31T13:14:45+00:00 Skoh 101289702+SkohTV@users.noreply.github.com 2025-03-31T13:14:45+00:00 4dabeff308222307ede8e74a2bd341713a7f7d81 Problem: Upon receiving a deadly signal, Nvim doesn't write buffers even if the option 'autowriteall' is set. Solution: Write to all writable buffers upon SIGHUP or SIGQUIT (but not SIGTERM), if the option 'autowriteall' is set. Co-authored-by: Justin M. Keyes <justinkz@gmail.com> 
Problem:
Upon receiving a deadly signal, Nvim doesn't write buffers even if
the option 'autowriteall' is set.

Solution:
Write to all writable buffers upon SIGHUP or SIGQUIT (but not
SIGTERM), if the option 'autowriteall' is set.

Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
 vim-patch:9.1.1260: Hang when filtering buffer with NUL bytes (#33192) 2025-03-30T13:41:05+00:00 zeertzjq zeertzjq@outlook.com 2025-03-30T13:41:05+00:00 431c037709d1e0e44a97b9eaa51afdc8354b492c Problem: Hang when filtering buffer with NUL bytes (after 9.1.1050). Solution: Don't subtract "written" from "lplen" repeatedly (zeertzjq). related: neovim/neovim#33173 closes: vim/vim#17011 https://github.com/vim/vim/commit/53fed23cb7bd59d9400961b44c6c8dca0029c929 
Problem:  Hang when filtering buffer with NUL bytes (after 9.1.1050).
Solution: Don't subtract "written" from "lplen" repeatedly (zeertzjq).

related: neovim/neovim#33173
closes: vim/vim#17011

https://github.com/vim/vim/commit/53fed23cb7bd59d9400961b44c6c8dca0029c929
 fix(terminal): delay when finishing terminal process #32846 2025-03-12T12:35:14+00:00 markstegeman markstegeman@users.noreply.github.com 2025-03-12T12:35:14+00:00 69a19295f8fe90356011eff2b7fa67b0593fffcc Problem: On Windows, the first attempt at finishing up after a terminal process terminates is delayed by 200ms, even if it would be possible to finish up immediately. Solution: Make the first attempt at finishing up immediately after the process terminates. 
Problem:
On Windows, the first attempt at finishing up after a terminal process
terminates is delayed by 200ms, even if it would be possible to finish
up immediately.

Solution:
Make the first attempt at finishing up immediately after the process
terminates.
 feat(ui): UI :detach command 2025-02-10T17:56:11+00:00 Justin M. Keyes justinkz@gmail.com 2025-02-09T21:04:33+00:00 4b0e2605eaf90268195029a29f10903dc82729e7 Problem: Cannot detach the current UI. Solution: - Introduce `:detach`. - Introduce `Channel.detach`. Co-authored-by: bfredl <bjorn.linse@gmail.com> 
Problem:
Cannot detach the current UI.

Solution:
- Introduce `:detach`.
- Introduce `Channel.detach`.

Co-authored-by: bfredl <bjorn.linse@gmail.com>
fix(messages): improve deadly signal messages #32364 2025-02-07T13:49:52+00:00 Justin M. Keyes justinkz@gmail.com 2025-02-07T13:49:52+00:00 ad853d1df093f30d0ca083a0c3a2935496533e8e Problem: Deadly signal messages mention "Vim", and add redundant newlines. Solution: - Update the messages. - Don't add an extra newline. 
Problem:
Deadly signal messages mention "Vim", and add redundant newlines.

Solution:
- Update the messages.
- Don't add an extra newline.
 docs: misc 2025-01-30T12:46:06+00:00 dundargoc gocdundar@gmail.com 2025-01-13T14:48:02+00:00 e71d2c817d1a2475551f58a98e411f6b39a5be3f Co-authored-by: Dustin S. <dstackmasta27@gmail.com> Co-authored-by: Ferenc Fejes <fejes@inf.elte.hu> Co-authored-by: Maria José Solano <majosolano99@gmail.com> Co-authored-by: Yochem van Rosmalen <git@yochem.nl> Co-authored-by: brianhuster <phambinhanctb2004@gmail.com> Co-authored-by: zeertzjq <zeertzjq@outlook.com> 
Co-authored-by: Dustin S. <dstackmasta27@gmail.com>
Co-authored-by: Ferenc Fejes <fejes@inf.elte.hu>
Co-authored-by: Maria José Solano <majosolano99@gmail.com>
Co-authored-by: Yochem van Rosmalen <git@yochem.nl>
Co-authored-by: brianhuster <phambinhanctb2004@gmail.com>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
vim-patch:partial:9.1.1050: too many strlen() calls in os_unix.c (#32188) 2025-01-24T00:52:55+00:00 zeertzjq zeertzjq@outlook.com 2025-01-24T00:52:55+00:00 2470db02c5136525b8abce1ee0889d94f8d81d98 Problem: too many strlen() calls in os_unix.c Solution: refactor os_unix.c and remove calls to strlen() (John Marriott) closes: vim/vim#16496 https://github.com/vim/vim/commit/efc41a5958bf25b352e0916af5f57dafbbb44f17 Omit os_expand_wildcards() change: Nvim's code is more complicated and harder to refactor. Co-authored-by: John Marriott <basilisk@internode.on.net> 
Problem:  too many strlen() calls in os_unix.c
Solution: refactor os_unix.c and remove calls to strlen()
          (John Marriott)

closes: vim/vim#16496

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

Omit os_expand_wildcards() change: Nvim's code is more complicated and
harder to refactor.

Co-authored-by: John Marriott <basilisk@internode.on.net>
 feat(tui): recognize X1 and X2 mouse events 2025-01-21T13:01:46+00:00 zeertzjq zeertzjq@outlook.com 2025-01-21T12:50:33+00:00 44dbfcfba4b09bb0e38f4a3f1960fa256a7bed71 Ref: https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Other-buttons 
Ref:
https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Other-buttons
feat(messages): add :!cmd shell message kinds 2025-01-15T09:51:52+00:00 Luuk van Baal luukvbaal@gmail.com 2025-01-14T11:05:23+00:00 5bae80899d9d29d80c129ca92cde75a1583b5efe Also print stderr error messages with ErrorMsg highlight group. 
Also print stderr error messages with ErrorMsg highlight group.