after/ftplugin configs are not respected

[sghng]

As mentioned in #526, it seems like some configs in after/ftplugin/codecompanion.{lua,vim} are not respected. Specifically I found that key mappings are effective, but anything related to set are not (e.g. set number).

I suspect that this has to do with the fact that CC chat buffers has buftype=nofile.

I saw some replies that the settings related to chat buffer can be configured in some undocumented plugin configs. They should of course be there if they're specific to the functioning of the chatting, but for things like set number, set colorcolumn, they should be configured like any other filetypes.

[olimorris]

Happy to accept a PR for this alongside the disabling of the defaults in the config

[sghng]

The problem seems to be that cc changes behavior of chat interface on a window level, i.e. via M.set_win_options(winnr, opts.opts), which overrides the filetype settings, which operate on a buffer level.

[olimorris]

I'm very much out of my knowledge zone here. We could detect the files with something like vim.api.nvim_get_runtime_file("after/ftplugin/codecompanion.lua", true). Perhaps on that basis we don't do any of the chat buffer formatting.

[olimorris]

This has now been fixed in #2251