mirror of
https://github.com/NotAShelf/neovim-flake.git
synced 2025-01-10 15:49:48 +01:00
statusline/feline: add components
This commit is contained in:
parent
970af589ad
commit
b3b8d3a86c
1 changed files with 19 additions and 4 deletions
|
@ -5,7 +5,7 @@
|
|||
}: let
|
||||
inherit (builtins) elem;
|
||||
inherit (lib.options) mkOption mkEnableOption literalExpression;
|
||||
inherit (lib.types) str listOf attrsOf anything either submodule;
|
||||
inherit (lib.types) str listOf attrs attrsOf anything either submodule;
|
||||
inherit (lib.lists) optional;
|
||||
inherit (lib.generators) mkLuaInline;
|
||||
inherit (lib.nvim.types) mkPluginSetupOption;
|
||||
|
@ -119,11 +119,26 @@ in {
|
|||
mode using `require('feline.providers.vi_mode').get_mode_color()`.
|
||||
|
||||
See `:help feline-vi-mode` for more details on vi mode.
|
||||
|
||||
|
||||
|
||||
'';
|
||||
};
|
||||
|
||||
# TODO:
|
||||
# - Check for the number of elements in the list maybe? Can Feline have infinite components per section?
|
||||
# - type-check contents of `attrsOf anything`? Is there a downside for not doing that?
|
||||
# - add examples for each one of those components. The option types are necessary, but confusing.
|
||||
components = {
|
||||
active = mkOption {
|
||||
type = listOf (listOf (attrsOf anything));
|
||||
default = [];
|
||||
description = "List of components to display for buffers feline will render as 'active'";
|
||||
};
|
||||
|
||||
inactive = mkOption {
|
||||
type = listOf (listOf (attrsOf anything));
|
||||
default = [];
|
||||
description = "List of components to display for buffers feline will render as 'inactive'";
|
||||
};
|
||||
};
|
||||
};
|
||||
};
|
||||
}
|
||||
|
|
Loading…
Reference in a new issue