Do not use { and } keymaps to switch chats, as they are default vim navigation keymaps

[paulodiovani]

Default keymaps for next/previous chat are } and {, but these are standard vim navigation keymaps (e.g. https://vimhelp.org/motion.txt.html#%7D).

Using it for something else breaks standard navigation.

Code is here:

codecompanion.nvim/lua/codecompanion/config.lua

Lines 290 to 305 in 41108b2

	next_chat = {
	modes = {
	n = "}",
	},
	index = 11,
	callback = "keymaps.next_chat",
	description = "Next Chat",
	},
	previous_chat = {
	modes = {
	n = "{",
	},
	index = 12,
	callback = "keymaps.previous_chat",
	description = "Previous Chat",
	},

Request

• change default keymaps to switch chats to other keys.

Alternative

• Add prefix option keymaps, to be used for every keymap.
  e.g. prefix = <Leader>c would make <Leader>cd for debug, <Leader>ca to change adapter, etc.

[olimorris]

What else are you navigating to in the chat buffer? This shouldn't be an issue

[olimorris]

...or change the keymaps

[ro0gr]

Yeah, that's definitely an option, though it's not super user-friendly and can be unexpected, since it changes the underlying Neovim defaults.

[olimorris]

That's incorrect and unsure where you've got that from. All keymaps are scoped to CodeCompanion buffers.

[paulodiovani]

...or change the keymaps

Yeah, that's definitely an option, though it's not super user-friendly and can be unexpected, since it changes the underlying Neovim defaults.

I believe they suggested to change CodeCompanion keymaps. Which is what I did.

e.g.

    strategies = {
      chat = {
        keymaps = {
          next_chat = { modes = { n = '<A-Right>' } },
          previous_chat = { modes = { n = '<A-Left>' } },
        },
      },
    },

But I do think the plugin could have more sane mappings, not replacing nvim defaults.

gd is another one that defaults to go to declaration, although this one is not much useful in the Chat window.

[ro0gr]

That's incorrect and unsure where you've got that from. All keymaps are scoped to CodeCompanion buffers.

Ya, sorry, my statement wasn't precise(not a native speaker). Of course i meant this keymap behaves differently only in scope of the CodeCompanion window out of box. This is the concern.

Anyways, thanks for your great effort!