neovim/runtime/scripts/optwin.lua, branch master

feat(tui): restore 'ttyfast' to control tty requests #38699

2026-04-24T18:45:20Z

Problem: When running nvim on a remote machine over SSH, if there is high ping, then bg detection may not complete in time. This results in a warning every time nvim is started. #38648 Solution: Restore 'ttyfast' option and allow it to control whether or not bg detection is performed. Because this is during startup and before any user config or commands, we use the environment variable `NVIM_NOTTYFAST` to allow disabling `ttyfast` during initialization.

vim-patch:3918f32: runtime(doc): fix incorrect description of 'scrolloffpad'

2026-04-22T02:14:53Z

closes: vim/vim#20029 https://github.com/vim/vim/commit/3918f3232f874b3c96f8bfccc5049711f16c252e

vim-patch:9.2.0356: Cannot apply 'scrolloff' context lines at end of file

2026-04-22T02:14:52Z

Problem: Cannot apply 'scrolloff' context lines at end of file Solution: Add the 'scrolloffpad' option to keep 'scrolloff' context even when at the end of the file (McAuley Penney). closes: vim/vim#19040 https://github.com/vim/vim/commit/a414630393f81c9a5b8fa4d0fcc1287155f67751 Co-authored-by: McAuley Penney

feat(options): add 'winpinned' to pin a window #39157

2026-04-20T00:36:55Z

Problem: - Unable to "pin" a window to prevent closing without specifically being targeted. - :fclose closes hidden windows (even before visible windows). Solution: - Add 'winpinned' window-local option. When set, window is skipped by :fclose and :only. Pin the ui2 cmdline window (which should always be visible), so that it is not closed by :only/fclose. - Skip over hidden (and pinned) windows with :fclose. Co-authored-by: glepnir

feat(lua): replace `buffer` with `buf` in vim.keymap.set/del #38360

2026-03-21T16:00:06Z

The `buffer` option remains functional but is now undocumented. Providing both will raise an error. Since providing `buf` was disallowed before, there is no code that will break due to using `buffer` alongside `buf`.

docs: lsp, options, promptbuf

2026-02-12T12:46:45Z

Close #37630 Close #37682 Close #37762 Close #37785 Co-authored-by: Daniel Schmitt Co-authored-by: Duane Hilton Co-authored-by: NeOzay Co-authored-by: Yi Ming Co-authored-by: "Justin M. Keyes"

vim-patch:9.1.1933: completion: complete_match() is not useful (#36726)

2025-11-28T02:10:31Z

Problem: completion: complete_match() Vim script function and 'isexpand' option are not that useful and confusing (after v9.1.1341) Solution: Remove function and option and clean up code and documentation (Girish Palya). complete_match() and 'isexpand' add no real functionality to Vim. They duplicate what `strridx()` already does, yet pretend to be part of the completion system. They have nothing to do with the completion mechanism. * `f_complete_match()` in `insexpand.c` does not call any completion code. It’s just a `STRNCMP()` wrapper with fluff logic. * `'isexpand'` exists only as a proxy argument to that function. It does nothing on its own and amounts to misuse of a new option. The following Vim script function can be used to implement the same functionality: ```vim func CompleteMatch(triggers, sep=',') let line = getline('.')->strpart(0, col('.') - 1) let result = [] for trig in split(a:triggers, a:sep) let idx = strridx(line, trig) if l:idx >= 0 call add(result, [idx + 1, trig]) endif endfor return result endfunc ``` related: vim/vim#16716 fixes: vim/vim#18563 closes: vim/vim#18790 https://github.com/vim/vim/commit/cbcbff871224115c45bbd14582749a487c6fad30 Co-authored-by: Girish Palya

vim-patch:9.1.1930: completion: 'completefuzzycollect' is too obscure

2025-11-27T23:53:49Z

Problem: completion: 'completefuzzycollect' option is too obscure Solution: Deprecate the option, but don't error out for existing scripts, behave like 'completefuzzycollect' is set when fuzzy completion is enabled (Girish Palya). fixes: vim/vim#18498 closes: vim/vim#18788 https://github.com/vim/vim/commit/33fbfe003c17ad25bf3903aaa89a55fe372086ba Remove this option completely, as it's introduced in Nvim v0.12 cycle. Co-authored-by: Girish Palya

vim-patch:9.1.1924: 'commentstring' requires +folding feature (#36645)

2025-11-21T00:24:20Z

Problem: 'commentstring' requires the +folding feature but is used in contexts other than folding. Solution: Remove the +folding feature guards from 'commentstring' and make it available in all builds (Doug Kearns). closes: vim/vim#18731 https://github.com/vim/vim/commit/a08030c9f729a133da552b5658e5b59c54581c79 Co-authored-by: Doug Kearns

refactor!: optwin.lua #36505

2025-11-20T04:43:15Z

Co-authored-by: zeertzjq Co-authored-by: Justin M. Keyes