Closed wosym closed 1 year ago
Commentary doesn't directly use 'filetype'
but rather 'commentstring'
, which is typically set by the ftplugin. My guess is you're missing filetype plugin indent on
in your vimrc. (Many installs enable this in the system vimrc, so that's probably why the issue is specific to one machine.)
I've used this plugin on several machines for quite some time now, and it works flawlessly on all filetypes I work with.
On one machine however, it does not appear to use the filetype properly. I'm not sure yet why.
For example,
:set filetype?
returnsfiletype=python
, which should be supported. However, it still adds C-type comments (/ --- /) when typinggcc
Not sure what's causing this bug. Is there a way to show what filetype commentary has detected and is using?