A minimal, stylish and customizable statusline for Neovim written in Lua
Requires Neovim >= 0.5
Feline is a Lua statusline that prioritizes speed, customizability and minimalism. It's blazing fast and never gets in your way. Feline only provides you with the necessary tools that you need to customize the statusline to your liking and avoids feature-bloat. It's also extremely customizable and allows you to configure it in any way you wish to. Feline also has reasonable defaults for those who don't want to configure things and just want a good out of the box experience.
-
Ease-of-use.
-
Complete customizability over every component.
-
Built-in providers such as:
- Vi-mode
- File info
- Cursor position
- Diagnostics (using Neovim's built-in LSP)
- Git branch and diffs (using gitsigns.nvim)
and many more
-
Minimalistic, only provides the bare minimum and allows the user to build their own components very easily.
- Necessary
- Neovim v0.5 or greater
- You must have 24-bit RGB color enabled in Neovim (do
:help 'termguicolors'in Neovim for more info)
- Optional
- nvim-web-devicons - For icon support
- A patched font - For icon support
- gitsigns.nvim - For git providers
NOTE: Some of these configurations may be outdated and may need to be changed prior to use. A few of the configurations are missing a link because the link to them was removed due to the link no longer being valid.
Default setup:
Default no-icons setup:
Config by luizcoro2:
Config by rafamadriz (classic):
Gruvbox:
Nord:
Config by rafamadriz (slant):
Gruvbox:
Nord:
Config by rafamadriz (VSCode):
Config by EdenEast (Colors generated from applied colorscheme)
Nightfox
Dayfox
You can add your own configuration to this list. If you're interested, simply make a Pull Request and I'll add it.
use 'feline-nvim/feline.nvim'Plug 'feline-nvim/feline.nvim'-- Replace 0.1 with your preferred version
use { 'feline-nvim/feline.nvim', tag = 'v0.1' }"" Replace 0.1 with your preferred version
Plug 'feline-nvim/feline.nvim', { 'tag': 'v0.1' }NOTE: The develop branch is intended for those who either wish to contribute to Feline or want the absolute bleeding edge version of Feline. The develop branch may contain changes that have not been tested thoroughly and therefore stability is not guaranteed. Moreover, commit history of the develop branch may be rewritten at any time. So use it at your own risk.
use { 'feline-nvim/feline.nvim', branch = 'develop' }Plug 'feline-nvim/feline.nvim', { 'branch': 'develop' }Once you've installed Feline, it's extremely easy to get started with it. If you don't mind using the default settings, you can just call Feline's setup() function in your configuration. Like this:
require('feline').setup()And that's it! It's as easy as that. In case you don't like icons and want to use the default statusline configuration but without icons, just do:
require('feline').setup({
preset = 'noicon'
})If the default configuration doesn't fit your needs and you want to build your own statusline configuration, it's highly recommended to configure Feline to suit your needs. The only prerequisite is knowing the basics of Lua. Feline provides a ton of configuration options which can let you build your statusline exactly how you want it as long. To see how to do that, take a look at USAGE or use :help feline.txt inside Neovim to read the USAGE documentation.
This can be caused if you forget to remove your other statusline plugins after installing Feline. Make sure all other statusline plugins are removed before you install Feline, that should fix the issue.
If you have an issue that you can't find the fix to in the documentation or want to request a feature you think is absolutely necessary, feel free to make a new Issue and I will try my best to look into it. If you want to contribute to Feline, you can make a Pull Request. For more details, please see: CONTRIBUTING
Now, you might be thinking, why do we need another statusline plugin? We've already got a bunch of brilliant statusline plugins like galaxyline, airline, lualine, expressline etc. and all of them are excellent. So then, why Feline?
I'd like the preface this by saying that what I'm about to say can be (and probably is) very biased and opinionated. Take what's being said here with a grain of salt. All of this is purely my opinion and not a fact by any means, so it's fine to disagree. Moreover, any statement I make here may be incorrect or outdated. In which case, please feel free to make an Issue or Pull Request correcting it.
I think that despite those plugins being neat, each have their own shortcomings. I find those shortcomings as too much to ignore. For example, most of the statusline plugins are not very customizable and the plugins only provide a limited amount of tools and options for customization. Feline, on the other hand, is built for customizability from the ground up. You are not limited in any way by what the plugin provides. You can control every individual component and its location, appearance, everything about it.
Feline is also fast and never gets in your way. It lazy-loads most of its modules, which allows it to start up instantly. Statusline updates with Feline are also blazing fast, which provides for a really smooth experience.
Feline is minimal and only implements the bare minimum required for you to get started. It both expects and invites you to make your own components and providers, because nobody understands you better than yourself. To help you do that, Feline provides all the tools and options you would need while also giving you a solid foundation to build from. One could say that the real goal of Feline is to make creating your own statusline as easy for you as possible, while also providing reasonable defaults that should be enough for most people.
Documentation is another aspect where I found most statusline plugins to be very lacking. Feline is extremely easy to configure and well-documented, which allows anyone to be able to build their statusline as they wish to. It provides example for every option to allow anyone to easily understand the purpose of any option
Lastly, anyone is welcome to contribute to Feline, either by making an Issue or through a Pull Request (see CONTRIBUTING for further information). Any kind of contribution starting from fixing a minor typo to adding a massive new feature is welcome.
And this plugin is named after cats, you won't get that anywhere else.
Feline is licensed under GNU GPLv3. For more info, see: LICENSE.md.
The name of this plugin is a silly pun based on the convention of the names of statusline plugins ending with 'line', while also being named after cats. And in a way this statusline is supposed to be as quick as a cat's instincts, so I guess the name fits.
Feline uses Semantic Versioning for its version names. This is meant to ensure that releases after 1.0 do not break backwards compatibility without a MAJOR version bump, thus allowing users to have better control over when they want to install a change that might potentially break their workflow.
