feat: add configs in setup

[mikesmithgh]

See #12 (comment)

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 📦🚀