rneovim.git/runtime/ftplugin/c.lua, branch master Neovim fork with Rahm's personal hacks. fix(runtime): treat b:undo_ftplugin consistently in Lua ftplugins (#30473) 2024-09-23T08:49:34+00:00 zeertzjq zeertzjq@outlook.com 2024-09-23T08:49:34+00:00 50577534318bbf8c1e22e80a74baa3b20c131ea8 - Don't assume b:undo_ftplugin is set when first modifying it. - Don't assume b:undo_ftplugin already contains some resetting. 
- Don't assume b:undo_ftplugin is set when first modifying it.
- Don't assume b:undo_ftplugin already contains some resetting.
 fix(runtime): update b:undo_ftplugin in Lua runtime files (#29529) 2024-07-01T09:48:09+00:00 zeertzjq zeertzjq@outlook.com 2024-07-01T09:48:09+00:00 8f5e90811025bcc652146168d5116f8d73fe8f81 Related to #29506, but adding vim.treesitter.stop() to b:undo_ftplugin doesn't solve the problem yet. 
Related to #29506, but adding vim.treesitter.stop() to b:undo_ftplugin
doesn't solve the problem yet.
 feat(ftplugin): change 'commentstring' to `// %s` for C/C++ (#29085) 2024-06-03T07:48:43+00:00 Soham Shanbhag sohamshanbhag@users.noreply.github.com 2024-06-03T07:48:43+00:00 054a287dbe6fe4308d26ec593da2057641f2bb9b Problem: The default commentstring for C/C++ can lead to invalid code when commenting and does not match the Nvim codebase. Solution: Change commentstring to `// %s` as used by Neovim. Also set all commentstrings that derive from the default C string explicitly (and correctly). 
Problem: The default commentstring for C/C++ can lead to invalid code 
when commenting and does not match the Nvim codebase.

Solution: Change commentstring to `// %s` as used by Neovim. Also
set all commentstrings that derive from the default C string explicitly
(and correctly).
refactor(defaults): do not use C specific default values for options (#22500) 2023-06-06T16:26:29+00:00 Gregory Anders 8965202+gpanders@users.noreply.github.com 2023-06-06T16:26:29+00:00 fcfe535e9877cfdc824dc78f2d19e590400d34cd The options 'path', 'include', and 'define' all use C-specific default values. This may have made sense a long time ago when Vim was mostly used just for writing C, but this is no longer the case, and we have ample support for filetype specific configuration. Make the default values of these options empty and move the C-specific values into a filetype plugin where they belong. Co-authored-by: zeertzjq <zeertzjq@outlook.com> 
The options 'path', 'include', and 'define' all use C-specific default
values. This may have made sense a long time ago when Vim was mostly
used just for writing C, but this is no longer the case, and we have
ample support for filetype specific configuration. Make the default
values of these options empty and move the C-specific values into a
filetype plugin where they belong.

Co-authored-by: zeertzjq <zeertzjq@outlook.com>
 refactor(defaults)!: change default 'commentstring' value to empty (#22862) 2023-04-02T15:01:48+00:00 zeertzjq zeertzjq@outlook.com 2023-04-02T15:01:48+00:00 269dd747b6e61842856031ca14ac26ee884ede4c