nyx VS feline.nvim

Here is a link to my dotfiles managed by nix. My setup is well structured and commented for others. It also has a lot of useful lua libraries and extensions functions that might be useful for others.

The right file tree is nvim-tree. The status line at the top is called a tabline. The tabline I am using is tabby.nvim. I do use tmux as well but this picture does not have a tmux session attached. You can find my configuration for tabby here. For my statusline I use feline and you can find my configuration for feline here. Note that for both tabline and statusline my config generates its own highlight groups based on my current theme. This is done here

You can check out my config here. The relevant sections are reload.lua and bootstrap.lua.

If you are interested in the complete setup you can find my config here: nyx. For the individual action components (as of time of writing):

If you would like to see a more complete setup/structure of a nix configuration you can check out mine: nyx

I was able to get something to work. For those who stumble upon this here is an example nyx

You can use flakes and home-manager. If you want an example of how to structure/setup your configuration you can check mine EdenEast/nyx. My configuration defines my nixos machines, darwin machines, and generic home-manager output (used for things like wsl).

Current config [nix](https://github.com/edeneast/nyx)

If you are looking for an example of a fully lua configuration that I hope is well structured you can check out my neovim config nyx

I also generate highlight groups based on the current colorscheme. I do this for my feline status line and tabby bar. You can see that in my config.

https://github.com/feline-nvim/feline.nvim is archived since 17 Feb 2023

I'm using feline.nvim but this question isn't specific to feline.

I use feline to generate my statusline and my winbar. This is imho the best statusline plugin for neovim in terms of configuration, truncation, default providers etc.

The "look" you're looking for is given by a bunch of plugins: - OneDark.nvim as colorscheme - TS Rainbow for rainbow brackets - BarBar for bufferline - Nvim Devicons and NerdFonts to view file icons - NvimTree as a file manager - Indent Blankline to show indentation guides - CompetiTest with vertical split UI - Feline as statusline plugin. In the screenshot feline is configured with a custom theme. As you can see statusline is different for CompetiTest buffers: a different statusline can be configured for every different filetype using conditional_config.

We have now migrated from feline to heirline

Pretty sure it isn't. Siduck used to use feline.nvim then later moved onto creating their own statusline that is specific to NvChad. You can find it here.

Hi! I'm a big fan of the feline plugin to describe a statusline. It provides a very powerful api to create your own components, which can be used in the statusline. But also, I like a way of the lualine, in which we can separate the schema of the statusline and used components. So, I've tried to combine these advantages in one place and wrote an extension for feline: dokwork/feline-theme.

Author of Feline.nvim and also the winbar PR here. I want to inform everyone who uses Feline that it now has support for winbar.

Packer failed to update feline.nvim, and I saw that it's been moved to https://github.com/feline-nvim/feline.nvim.

Hello, author of Feline.nvim here. I'll get straight to the point. A while ago I started using Semantic Versioning for Feline.nvim as it seemed like a good idea at that time. However, as time went by, it just became more and more of a hassle to release new versions, especially after development of Feline.nvim slowed down and it just needed minor bugfixes. I feel like now it's more hassle than it's worth. So I'm switching back to using a rolling-release model. From now on, the master branch will contain the latest changes. The development branch is deprecated and all development branch users need to switch to the master branch.