4 Commits

Author	SHA1	Message	Date
zeertzjq	8f5e908110	fix(runtime): update b:undo_ftplugin in Lua runtime files (#29529) ... Related to #29506, but adding vim.treesitter.stop() to b:undo_ftplugin doesn't solve the problem yet.	2024-07-01 17:48:09 +08:00
Soham Shanbhag	054a287dbe	feat(ftplugin): change 'commentstring' to // %s for C/C++ (#29085) ... 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).	2024-06-03 09:48:43 +02:00
Gregory Anders	fcfe535e98	refactor(defaults): do not use C specific default values for options (#22500) ... 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>	2023-06-06 11:26:29 -05:00
zeertzjq	269dd747b6	refactor(defaults)!: change default 'commentstring' value to empty (#22862)	2023-04-02 23:01:48 +08:00