rneovim.git/runtime/ftplugin/css.lua, branch rahm Neovim fork with Rahm's personal hacks. vim-patch:9.1.0464: no whitespace padding in commentstring option in ftplugins 2024-06-04T08:38:55+00:00 Christian Clason c.clason@uni-graz.at 2024-06-04T07:39:28+00:00 2f5b8a009280eba995aecf67d1e8d99b7c72c51c Problem: no whitespace padding in commentstring option in ftplugins Solution: Change default to include whitespace padding, update existing filetype plugins with the new default value (Riley Bruins) closes: vim/vim#14843 https://github.com/vim/vim/commit/0a0830624a260660c7fa692ecb7e6e5de09114ba Co-authored-by: Riley Bruins <ribru17@hotmail.com> 
Problem:  no whitespace padding in commentstring option in ftplugins
Solution: Change default to include whitespace padding, update
          existing filetype plugins with the new default value
          (Riley Bruins)

closes: vim/vim#14843

https://github.com/vim/vim/commit/0a0830624a260660c7fa692ecb7e6e5de09114ba

Co-authored-by: Riley Bruins <ribru17@hotmail.com>
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)!: 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