Open vhyrro opened 4 months ago
Why not add this to rocks-config?
I did consider that but that sounds out of the scope of rocks-config itself. I feel like rocks-config should just do plugin configuration, not Neovim configuration
But it's rocks-config, not rocks-plugin-config :sweat_smile: I don't feel strongly about this.
Wouldn't this add unnecessary complexity?
Setting vim options is quite straightforward, wrapping it inside a plugin would mean that we are mapping between config and vim option which could be avoided just by explicitly setting the option.
Wouldn't this add unnecessary complexity?
It adds a tiny amount overhead, and nobody's forced to use it. I wouldn't necessarily call it "complexity".
Since we're already using TOML for a lot of things, perhaps it would be wise to create a module that can also manage various aspects of the configuration (options, colourschemes).
I can't settle on a name, as
rocks-config
is taken. This would either parse therocks.toml
file or would parse a new, unrelatedconfig.toml
file with all of the metadata there. This may overlap with nvim-neorocks/rocks.nvim#240.Example: