-
Notifications
You must be signed in to change notification settings - Fork 92
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
feature: nvim-lualine
component
#259
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Hi @folke any chance you can take a quick look? |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
just a ping |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
this starts to be a very boring action... |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
Sigh |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
I am here again |
Did you check the docs?
Is your feature request related to a problem? Please describe.
👋 Hi!
Thoughts on providing a
lualine
component that would display the number of TODOs, NOTEs, etc. to the user's liking?Describe the solution you'd like
Ideally, this plugin can provide a component (e.g. a Lua function returning a string) that can be added to any segment in
lualine
e.g.The ideal result would be something like:
...or whatever the glyphs this plugin is configured with.
Describe alternatives you've considered
I wrote a plugin to do this (https://github.com/bezhermoso/todos-lualine.nvim), but it maintains its own copy of this plugin's defaults e.g. glyphs, keywords for each type. Users that override these settings would need to replicate the config for the component to maintain consistency. Not so bad for glyphs, but inconsistency arising from diverging sets of keywords is not good.
Ideally, there is a single configuration that's respected in both the functionality-proper & the
lualine
component.Alternatively:
This plugin can provide a Lua API to fetch the number of matches given a list of todo-types e.g.
fetch_counts({"TODO", "FIX"}, callback)
& expose the counts in a structured way, or simply expose the user's configuration so thattodos-lualine
can read & use it.Additional context
No response
The text was updated successfully, but these errors were encountered: