Replies: 1 comment
-
Thanks for your hardwork and thoughtful comments. I completely see how currently this could be a big inconvenience. If you want to draft up a PR I'd be happy to take a look at it and start using it in my workflow to throughly test it out. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Using 'markdown' as the filetype for codecompanion chat buffers can provide better compatibility with existing Markdown tools and settings. While setting filetype to 'codecompanion' helps distinguish the chat buffer from other normal buffers, it breaks several markdown features:
$|$
and_|_
) does not work in chat buffersMaking all the above work in codecompanion buffers is possible but requires many extra tweaks and even hacks since they are originally designed for markdown files.
Instead, we can set the filetype to 'markdown' and use a buffer-local variable
vim.b.codecompanion
to identify codecompanion buffers. This maintains full markdown compatibility while still allowing codecompanion-specific customization.This could be made opt-in to avoid breaking existing setups. I have a working draft of this implementation (refactor needed to make it tidier):
Beta Was this translation helpful? Give feedback.
All reactions