<feed xmlns='http://www.w3.org/2005/Atom'>
<title>neovim/runtime/lua/vim/_meta/options.gen.lua, branch marvim/ci-version-update</title>
<subtitle>Vim-fork focused on extensibility and usability</subtitle>
<id>http://git.waynecole.info/neovim/atom?h=marvim%2Fci-version-update</id>
<link rel='self' href='http://git.waynecole.info/neovim/atom?h=marvim%2Fci-version-update'/>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/'/>
<updated>2026-04-24T18:45:20Z</updated>
<entry>
<title>feat(tui): restore 'ttyfast' to control tty requests #38699</title>
<updated>2026-04-24T18:45:20Z</updated>
<author>
<name>Kyle</name>
<email>50718101+kylesower@users.noreply.github.com</email>
</author>
<published>2026-04-24T18:45:20Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=66149ca6681102ff758b516984a1ccfe2ce0d974'/>
<id>urn:sha1:66149ca6681102ff758b516984a1ccfe2ce0d974</id>
<content type='text'>
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.</content>
</entry>
<entry>
<title>fix(options): default 'titlestring' shows CWD #39233</title>
<updated>2026-04-22T09:56:23Z</updated>
<author>
<name>Nick Krichevsky</name>
<email>njk828@gmail.com</email>
</author>
<published>2026-04-22T09:56:23Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=e68e76935267afbf84bff9fffa69f963ebce0f5a'/>
<id>urn:sha1:e68e76935267afbf84bff9fffa69f963ebce0f5a</id>
<content type='text'>
Problem:
In the default 'titlestring', if the containing directory is the CWD, it renders as "."

Solution:
Add `:p` to the titlestring.</content>
</entry>
<entry>
<title>vim-patch:9.2.0356: Cannot apply 'scrolloff' context lines at end of file</title>
<updated>2026-04-22T02:14:52Z</updated>
<author>
<name>zeertzjq</name>
<email>zeertzjq@outlook.com</email>
</author>
<published>2026-04-20T12:47:50Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=8f1e14ffa28787fc4faa8b645f378c23735f5bbe'/>
<id>urn:sha1:8f1e14ffa28787fc4faa8b645f378c23735f5bbe</id>
<content type='text'>
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 &lt;jacobmpenney@gmail.com&gt;
</content>
</entry>
<entry>
<title>docs: misc #39207</title>
<updated>2026-04-20T11:09:37Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2026-04-20T11:09:37Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=2b52acfb8a6c43db0e31abe8975330ea3363bd5d'/>
<id>urn:sha1:2b52acfb8a6c43db0e31abe8975330ea3363bd5d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>feat(options): add 'winpinned' to pin a window #39157</title>
<updated>2026-04-20T00:36:55Z</updated>
<author>
<name>luukvbaal</name>
<email>luukvbaal@gmail.com</email>
</author>
<published>2026-04-20T00:36:55Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=fe986e5dd094b2f7e1d28e64e52ffbc5f7292191'/>
<id>urn:sha1:fe986e5dd094b2f7e1d28e64e52ffbc5f7292191</id>
<content type='text'>
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 &lt;glephunter@gmail.com&gt;</content>
</entry>
<entry>
<title>docs: misc #39045</title>
<updated>2026-04-18T19:38:59Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2026-04-18T19:38:59Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=54398c587473c0f1d96b601a281477e184865401'/>
<id>urn:sha1:54398c587473c0f1d96b601a281477e184865401</id>
<content type='text'>
</content>
</entry>
<entry>
<title>docs: lsp, options, api #38980</title>
<updated>2026-04-14T10:09:54Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2026-04-14T10:09:54Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=d77808ec59be2428f03fc43489ec70dcb71ac572'/>
<id>urn:sha1:d77808ec59be2428f03fc43489ec70dcb71ac572</id>
<content type='text'>
docs: lsp, options

- revert bogus change to `_meta/builtin_types.lua` from 3a4a66017b74

Close #38991

Co-authored-by: David Mejorado &lt;david.mejorado@gmail.com&gt;</content>
</entry>
<entry>
<title>fix(lua): not obvious which _meta/ files are generated #39035</title>
<updated>2026-04-14T09:38:47Z</updated>
<author>
<name>Justin M. Keyes</name>
<email>justinkz@gmail.com</email>
</author>
<published>2026-04-14T09:38:47Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/neovim/commit/?id=65b40e69acbcb28c0e7ef9228f731c444a788e93'/>
<id>urn:sha1:65b40e69acbcb28c0e7ef9228f731c444a788e93</id>
<content type='text'>
Problem:
- Not obvious which _meta/ are generated and which should be edited
  manually.
- The require guard (`error('Cannot require a meta file')`) is not
  consistently present in all meta files.

Solution:
- Update headers.
- Add require() guard to all meta files.
- Rename generated meta files with `.gen.lua`.</content>
</entry>
</feed>
