A collection of pre-built, distro-agnostic UI components for customizing Neovim's statusline, winbar, tabline, and statuscolumn with Heirline.
heirline-components.nvim is a Neovim plugin that offers a comprehensive set of pre-built UI components designed for use with the Heirline engine. It solves the complexity of manually crafting statuslines, winbars, tablines, and statuscolumns by providing modular, tested components that can be easily customized and integrated into any Neovim configuration.
Neovim users who want to customize their editor's UI without building components from scratch, particularly those using or interested in the Heirline engine for creating flexible, performant interfaces.
Developers choose heirline-components.nvim for its extensive library of ready-to-use components, distro-agnostic design, and ease of customization, which significantly reduces the time and effort required to create a polished, functional Neovim UI compared to starting from scratch with Heirline alone.
Distro agnostic components for your Neovim heirline config
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides ready-to-use components for all Neovim UI areas—tabline, winbar, statuscolumn, and statusline—covering everything from Git status to LSP clients, as detailed in the Components section.
Allows straightforward overrides of default icons and colors through the opts table, exemplified in the Available options section with code snippets.
Enhances functionality by integrating with popular plugins like gitsigns.nvim and compiler.nvim, though this requires their installation, as noted in the README.
Automatically refreshes the UI in response to Neovim events such as ColorScheme, ensuring visual consistency without manual intervention.
Full feature set depends on several external plugins like gitsigns.nvim and compiler.nvim, which can bloat the setup and increase maintenance.
Requires users to understand Heirline's configuration model to effectively assemble and customize components, adding a learning barrier.
Component details are linked to separate wiki pages, making it less convenient to browse compared to having all documentation in the main README.