Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
When I think of "Lines and Bars" I usually think of "Statuslines", "Win Bars" and "Tab Bars", but I noticed that there are other plugins that don't fit that definition, mostly the ones at the beginning of the sections (like the ones that change colorcolumn, for instance).
How should we treat those plugins?
Originally created by @Penaz91 on GitHub (Apr 27, 2026).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/2290
Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
When I think of "Lines and Bars" I usually think of "Statuslines", "Win Bars" and "Tab Bars", but I noticed that there are other plugins that don't fit that definition, mostly the ones at the beginning of the sections (like the ones that change `colorcolumn`, for instance).
How should we treat those plugins?
The safest bet would be to move them to the UI section, unless we decide to create a new one for colorcolumn (or something like that).
<!-- gh-comment-id:4330489543 -->
@DrKJeff16 commented on GitHub (Apr 27, 2026):
The safest bet would be to move them to the UI section, unless we decide to create a new one for colorcolumn (or something like that).
Yeah not sure why it's a category with subcategories compared to just breaking them out to their own things. One thing is the vim way is things are called lines and bar is maybe more used in other places. I think we can use line if it is line or bar.
Would say we can move them up to a main top level section and have the following:
Column (line numbers, statuscolumn)
Header Line or Bar (Breadcrumb/Winbar other terms), which could then include Tabline (just a bar across the top).
Statusline
Cursor (Cursor lines or just the cursor)
Only thing maybe is some of the plugins touch multiple of these (OXY2DEV/bars.nvim), so where do those go?
<!-- gh-comment-id:4332402257 -->
@rockerBOO commented on GitHub (Apr 28, 2026):
Yeah not sure why it's a category with subcategories compared to just breaking them out to their own things. One thing is the vim way is things are called lines and bar is maybe more used in other places. I think we can use line if it is line or bar.
Would say we can move them up to a main top level section and have the following:
- Column (line numbers, statuscolumn)
- Header Line or Bar (Breadcrumb/Winbar other terms), which could then include Tabline (just a bar across the top).
- Statusline
- Cursor (Cursor lines or just the cursor)
Only thing maybe is some of the plugins touch multiple of these (OXY2DEV/bars.nvim), so where do those go?
Only thing maybe is some of the plugins touch multiple of these (OXY2DEV/bars.nvim), so where do those go?
Agreed, this is a can of worms, potentially.
Should we go ahead with that, I think we should set specific (and reasonable) guidelines. This is to prevent headaches for us, plugin developers and users in general. For that we need to reach an agreement and (more likely than not) extend CONTRIBUTING.md and/or MAINTAINERS.md.
<!-- gh-comment-id:4333426766 -->
@DrKJeff16 commented on GitHub (Apr 28, 2026):
> Only thing maybe is some of the plugins touch multiple of these (OXY2DEV/bars.nvim), so where do those go?
Agreed, this is a can of worms, potentially.
Should we go ahead with that, I think we should set specific (and reasonable) guidelines. This is to prevent headaches for us, plugin developers and users in general. For that we need to reach an agreement and (more likely than not) extend `CONTRIBUTING.md` and/or `MAINTAINERS.md`.
Keep in mind colorcolumn should go here, if that's the case.
<!-- gh-comment-id:4333534308 -->
@DrKJeff16 commented on GitHub (Apr 28, 2026):
> * Column (line numbers, statuscolumn)
Keep in mind `colorcolumn` should go here, if that's the case.
My suggestion would be to move them to the UI section. Placing them in the UI section could potentially clear up some doubts users might have.
UI
...
Column
Winbar or Tabline
Statusline
Cursor
<!-- gh-comment-id:4333833587 -->
@DrKJeff16 commented on GitHub (Apr 28, 2026):
## Proposal
My suggestion would be to move them to the UI section. Placing them in the UI section could potentially clear up some doubts users might have.
- UI
- ...
- Column
- Winbar or Tabline
- Statusline
- Cursor
That was, kind of, what I was trying to get to in #1875
Nevertheless, my wording in my proposed list is not final, just a proof of concept.
<!-- gh-comment-id:4333991397 -->
@DrKJeff16 commented on GitHub (Apr 28, 2026):
_That was, kind of, what I was trying to get to in #1875_
Nevertheless, my wording in my proposed list is not final, just a proof of concept.
I think the issues expressed in #1875 remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
<!-- gh-comment-id:4338757307 -->
@Penaz91 commented on GitHub (Apr 28, 2026):
I think the issues expressed in #1875 remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
I think the issues expressed in #1875 remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
Agreed, I rescind my statements including >=3 levels.
<!-- gh-comment-id:4339103818 -->
@DrKJeff16 commented on GitHub (Apr 28, 2026):
> I think the issues expressed in [#1875](https://github.com/rockerBOO/awesome-neovim/issues/1875) remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
Agreed, I rescind my statements including >=3 levels.
@Penaz91 Could you help me with telling me which target plugin would belong in which subsection? I'm a little busy right now.
<!-- gh-comment-id:4369216728 -->
@DrKJeff16 commented on GitHub (May 4, 2026):
> * UI
> * Column
> * Winbar or Tabline
> * Statusline
> * Cursor
@Penaz91 Could you help me with telling me which target plugin would belong in which subsection? I'm a little busy right now.
@Penaz91 Could you help me with telling me which target plugin would belong in which subsection? I'm a little busy right now.
I will try and draft a PR in the next few days, thanks for the heads up.
<!-- gh-comment-id:4370904462 -->
@Penaz91 commented on GitHub (May 4, 2026):
> [@Penaz91](https://github.com/Penaz91) Could you help me with telling me which target plugin would belong in which subsection? I'm a little busy right now.
I will try and draft a PR in the next few days, thanks for the heads up.
I think the issues expressed in #1875 remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
Agreed, I rescind my statements including >=3 levels.
Tho most of merges are still valid, just don't add more nesting. Like Animation, Split and Window and maybe some others could still be moved into under UI. Moving Colorscheme also may work (this).
<!-- gh-comment-id:4571260307 -->
@sukineco commented on GitHub (May 29, 2026):
> > I think the issues expressed in [#1875](https://github.com/rockerBOO/awesome-neovim/issues/1875) remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
>
> Agreed, I rescind my statements including >=3 levels.
Tho most of merges are still valid, just don't add more nesting. Like _Animation_, _Split and Window_ and maybe some others could still be moved into under _UI_. Moving _Colorscheme_ also may work ([this](https://github.com/rockerBOO/awesome-neovim/issues/2336#issuecomment-4571149870)).
Moving Colorscheme to UI is not a good idea, despite our tagging system implemented not too long ago.
<!-- gh-comment-id:4572526639 -->
@DrKJeff16 commented on GitHub (May 29, 2026):
Moving Colorscheme to UI is not a good idea, despite our tagging system implemented not too long ago.
Moving Colorscheme to UI is not a good idea, despite our tagging system implemented not too long ago.
I agree, it is way too large to be a "subsection".
Will give a think about lots of stuff in the weekend, if life doesn't throw me curveballs like the last month or so.
<!-- gh-comment-id:4574847645 -->
@Penaz91 commented on GitHub (May 29, 2026):
> Moving Colorscheme to UI is not a good idea, despite our tagging system implemented not too long ago.
I agree, it is way too large to be a "subsection".
Will give a think about lots of stuff in the weekend, if life doesn't throw me curveballs like the last month or so.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Penaz91 on GitHub (Apr 27, 2026).
Original GitHub issue: https://github.com/rockerBOO/awesome-neovim/issues/2290
Originally assigned to: @rockerBOO, @Penaz91, @DrKJeff16 on GitHub.
When I think of "Lines and Bars" I usually think of "Statuslines", "Win Bars" and "Tab Bars", but I noticed that there are other plugins that don't fit that definition, mostly the ones at the beginning of the sections (like the ones that change
colorcolumn, for instance).How should we treat those plugins?
@DrKJeff16 commented on GitHub (Apr 27, 2026):
The safest bet would be to move them to the UI section, unless we decide to create a new one for colorcolumn (or something like that).
@rockerBOO commented on GitHub (Apr 28, 2026):
Yeah not sure why it's a category with subcategories compared to just breaking them out to their own things. One thing is the vim way is things are called lines and bar is maybe more used in other places. I think we can use line if it is line or bar.
Would say we can move them up to a main top level section and have the following:
Only thing maybe is some of the plugins touch multiple of these (OXY2DEV/bars.nvim), so where do those go?
@DrKJeff16 commented on GitHub (Apr 28, 2026):
Agreed, this is a can of worms, potentially.
Should we go ahead with that, I think we should set specific (and reasonable) guidelines. This is to prevent headaches for us, plugin developers and users in general. For that we need to reach an agreement and (more likely than not) extend
CONTRIBUTING.mdand/orMAINTAINERS.md.@DrKJeff16 commented on GitHub (Apr 28, 2026):
Keep in mind
colorcolumnshould go here, if that's the case.@DrKJeff16 commented on GitHub (Apr 28, 2026):
Proposal
My suggestion would be to move them to the UI section. Placing them in the UI section could potentially clear up some doubts users might have.
@Penaz91 commented on GitHub (Apr 28, 2026):
@DrKJeff16 Good idea. It would clear and bring order
@DrKJeff16 commented on GitHub (Apr 28, 2026):
That was, kind of, what I was trying to get to in #1875
Nevertheless, my wording in my proposed list is not final, just a proof of concept.
@Penaz91 commented on GitHub (Apr 28, 2026):
I think the issues expressed in #1875 remain, but if we manage to keep it to two levels at most I'm all for it. The naming looks good to me
@DrKJeff16 commented on GitHub (Apr 28, 2026):
Agreed, I rescind my statements including >=3 levels.
@DrKJeff16 commented on GitHub (May 4, 2026):
@Penaz91 Could you help me with telling me which target plugin would belong in which subsection? I'm a little busy right now.
@Penaz91 commented on GitHub (May 4, 2026):
I will try and draft a PR in the next few days, thanks for the heads up.
@sukineco commented on GitHub (May 29, 2026):
Tho most of merges are still valid, just don't add more nesting. Like Animation, Split and Window and maybe some others could still be moved into under UI. Moving Colorscheme also may work (this).
@DrKJeff16 commented on GitHub (May 29, 2026):
Moving Colorscheme to UI is not a good idea, despite our tagging system implemented not too long ago.
@Penaz91 commented on GitHub (May 29, 2026):
I agree, it is way too large to be a "subsection".
Will give a think about lots of stuff in the weekend, if life doesn't throw me curveballs like the last month or so.