Replies: 3 comments 2 replies
-
|
My concern with doing this now at this stage of the plugin is that it breaks functionality for users and I have to bump the version number. Given the ease (I hope) of changing the keymaps in your config I would assume anyone with an annoyance would change it. |
Beta Was this translation helpful? Give feedback.
-
|
I agree that you might keep this in the backlog/back of your head for a future breaking change. I'm a long-term Vim and NeoVim user and used to exit insert mode with Ctrl-C. So I accidentally exited the chat window way more than I'd like to. |
Beta Was this translation helpful? Give feedback.
-
|
For what it's worth, I think that mapping Ctrl-C to something that completely nukes the CodeCompletion chat buffer out of existence is completely bonkers, I've lost multiple conversations because of this (and it's very frustrating). Now, I don't think that functionality should exist at all, but if it is to exist, maybe map it to something that is not used as much? I don't use Ctrl-C to exit insert mode, but I do use it to stop commands in the command line, and since I'm human every now and then I accidentally press it while in CodeCompanion and boom, all gone. I'm probably not the only one. Good to know that this can be remapped, though. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Sometimes when you focus out of neovim and you focus back, you found yourself in insert mode and pressing ESC doesn't let you get out. So you use CTRL+C.
But if you were in the CodeCompanion chat window, the entire chat conversation is permanently deleted and removed from history. This results in loss of valuable data.
Can we make this an opt in functionality? Or change it from CTRL + C ? I have overriden the binding in my dotfiles, but I think we should prefer an healthy default anyways
Beta Was this translation helpful? Give feedback.
All reactions