nvim-lua VS feline.nvim

I recently converted vim-tmux-navigator to lua via a simple function and using A-hjkl\ binds (which has no conflicts) instead of the default C-hjkl\, feel free to reuse my code, relevant commit.

source: https://github.com/ibhagwan/nvim-lua/blob/main/lua/lsp/rename.lua

I guess this is a preference thing, I would consider my config my config highly customized and pretty advanced, it has almost 8k lines of code, I don't fiddle with it as much as when I just converted to lua but I still update ocasionally and I find lua perfect for the job, instead of macros I just create small lua functions in order to avoid code duplication (where applicable).

I'm not just giving you complements to boost your morale, I've seen your code first hand, I've used feline (we even interacted in issues) and also copied your archived nvim-reload code into my config and can recognize a good programmer when I see one.

Technically all you need to do is set package.loaded[module] = nil for all the modules you wish to reload and that's why my modded version does, it reloads all your entire neovim config and all the plugins listed in the linked init file.

FYI, just added this to my config with a slight twist (resize back once I'm done), this so great :)

My config isn’t a “permade”, it’s not meant to be a solution for anyone other than myself, nevertheless you might find it useful for plugin selection and some cool functions.

You can view my setup here.

My own version of Embark colorscheme and feline.nvim, my configuration can be found here

Btw, if anyone wants the “evil-line” equivalent config for feline you can find it here

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.