Don't override vim keybinds

[mikesmithgh]

Don't override vim keybinds

[musjj]

Yes, that sounds pretty good! Maybe also have a special default config key, that when specified, will get invoked when no --config is provided? But I'm just bikeshedding here, either way would be fine.

[mikesmithgh]

Hey @musjj , I released adding configs to your setup function in v2.0.0 let me know how this works for you 👍

[mikesmithgh]

Hey @musjj,

I have plans to add more detailed documentation and guides for configuring keymaps/options.

There are a couple things you can do at the moment.

Example disable all keymaps: https://github.com/mikesmithgh/kitty-scrollback.nvim/blob/main/lua/kitty-scrollback/configs/keymaps_disabled.lua
Example override keymaps: https://github.com/mikesmithgh/kitty-scrollback.nvim/blob/main/lua/kitty-scrollback/configs/keymaps_custom.lua

• <NOP> could also be used to disable certain keymaps (e.g., lua vim.keymap.set({ 'n' }, '<Plug>(KsbYankLine)', '<NOP>', {}))

If you run the command :KittyScrollbackGenerateKittens! it will display a list of kittens pointing to all of the example configs.

Those should allow you to reconfigure the default keymaps (https://github.com/mikesmithgh/kitty-scrollback.nvim/blob/main/lua/kitty-scrollback/keymaps.lua#L20).

Right now, yanks to the unnamed register are handled by an autocommand and not by a keymap. So that can't be configured, https://github.com/mikesmithgh/kitty-scrollback.nvim/blob/main/lua/kitty-scrollback/autocommands.lua#L165

• I could add an option to specify a register or nil to allow that to be configured or disabled. Is this something that you are interested in?

Appreciate the feedback 👍

[musjj]

Thanks, that's interesting, I didn't realize that the plugin uses a separate config file. Are there any plans to go with the conventional require("kitty-scrollback").setup(...) configuration method? That'd make configuration a lot easier.

I could add an option to specify a register or nil to allow that to be configured or disabled. Is this something that you are interested in?

Yes, it would be nice if there's an option to configure this too!

[mikesmithgh]

Thanks, that's interesting, I didn't realize that the plugin uses a separate config file. Are there any plans to go with the conventional require("kitty-scrollback").setup(...) configuration method? That'd make configuration a lot easier.

I originally used separate config files because the kitten (written in python) starts Nvim and passes kitty specific info as arguments. I did some experimenting and think I could get the conventional setup method to work and agree it would be cleaner.

require('kitty-scrollback').setup({
  default = function(kitty_data)
    return { ... default config here ... }
  end,
  another = function(kitty_data)
    return { ... another config here ... }
  end,
  ...
})

Then the kitten would be called like
kitty.conf

map ctrl+shift+h kitty_scrollback_nvim --config default
map f1 kitty_scrollback_nvim --config another

That way you could centralize all your configs in the setup and then specify the particular config by key. @musjj Does that sound like a good approach to you or do you have any other ideas?

Yes, it would be nice if there's an option to configure this too!

Nice, I'll add an issue for that

[mikesmithgh]

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[musjj]

Thank you!