-
-
Notifications
You must be signed in to change notification settings - Fork 190
statusline/feline: init #521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
77f52f7 to
b3b8d3a
Compare
| config = mkIf cfg.enable { | ||
| vim = { | ||
| lazy.plugins.feline-nvim = { | ||
| event = "UIEnter"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| event = "UIEnter"; | |
| event = "DeferredUIEnter"; |
This is debatable, but if the goal is to start accepting user input as soon as possible, then DeferredUIEnter should be used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a benefit to taking user input as soon as possible?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean yeah? You wouldn't want a 10s startup time would you
| enable = mkEnableOption "minimal, stylish and customizable statusline, statuscolumn, and winbar [feline.nvim]"; | ||
| setupOpts = mkPluginSetupOption "feline-nvim" { | ||
| custom_providers = mkOption { | ||
| type = attrsOf anything; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be of type luaInline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
custom_providers takes a table, in which case we should be able to get a listOf luaInline. No?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Men go read the docs, you have to be able to refer to the custom providers somehow. It's a set of functions (which is what I meant to say in my original comment, but it ended up beibg ambiguous)
|
|
||
| disable = mkOption { | ||
| default = {}; | ||
| type = attrsOf (submodule conditionalRenderers); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't make sense, the defaults above only apply to force_active. Nothing should be disabled by default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We cannot omit the default here. That's why it has one, and also conditionalRenderers submodule provides upstream defaults.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It literally does not, nothing is disabled by default (in the upstream detaults, which is what I meant by apply)
02ee4cc to
bc978c4
Compare
|
✅ Preview has been deleted successfully! |
Adds a module for feline.nvim. Should be done, but we'd like to add examples to
components.activeandcomponents.inactivebefore this can be merged.