nvim-neorocks / rocks-config.nvim

Allow rocks.nvim to help configure your plugins.
GNU General Public License v3.0
55 stars 2 forks source link

[Module]: helix-like configuration files #37

Open vhyrro opened 4 months ago

vhyrro commented 4 months ago

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 the rocks.toml file or would parse a new, unrelated config.toml file with all of the metadata there. This may overlap with nvim-neorocks/rocks.nvim#240.

Example:


[configuration]
colorscheme = "kanagawa"

[configuration.options]
termguicolors = true
concealcursor = "nv"
mrcjkb commented 4 months ago

Why not add this to rocks-config?

vhyrro commented 4 months ago

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

mrcjkb commented 4 months ago

But it's rocks-config, not rocks-plugin-config :sweat_smile: I don't feel strongly about this.

c3n21 commented 3 months ago

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.

mrcjkb commented 3 months ago

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".