fsread.nvim
feline.nvim
fsread.nvim | feline.nvim | |
---|---|---|
6 | 41 | |
137 | 1,021 | |
- | - | |
1.3 | 6.8 | |
about 1 year ago | about 1 year ago | |
Lua | Lua | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fsread.nvim
-
Introducing the bionic.nvim plugin: Enhancing readability of dense text in neovim for dyslexic individuals
Then there is easyread.nvim and fsread.nvim
-
Neovim Bionic Reading plugin!
APPRECIATION/CREDITS: So, thank you to u/JellyApple102 and u/catnvim for creating easyread.nvim and fsread.nvim respectively. I learned a lot reading through your plugins
-
easyread.nvim - bionic-like reading in Neovim
I also made fsread.nvim plugin 4 months ago
-
Feline.nvim is archived. You can blame reddit for this one
I sent the plugin author flair application 2 months ago and did not get any response. I have fsread.nvim with more than 100 stars so I think I'm eligible?
-
Authors: how do you make your plugin discoverable and appealing?
Look at your repo link you didn't deliver the dead simple promise, why do I have to call require("no-neck-pain").setup(), that's an extra step that I don't want to do if I wanna try your plugin, setup function should be optional. Take my fsread plugin for example, the selling point is a single source in plugin/ and nothing else.
-
fsread.nvim - flow state reading in neovim
Link: nullchilly/fsread.nvim
feline.nvim
-
Feline.nvim is archived. You can blame reddit for this one
https://github.com/feline-nvim/feline.nvim is archived since 17 Feb 2023
-
Fetching and displaying the latest message in my statusline with vim.o.cmdheight = 0
I'm using feline.nvim but this question isn't specific to feline.
-
reticle.nvim
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.
-
How to configure nvim UI to look like this?
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.
-
AstroNvim 2.4
We have now migrated from feline to heirline
-
Global statusilne lokos cool
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.
-
Extension for feline to describe your statusline in the lualine way
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.
-
Winbar support added for Feline.nvim
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.
-
PSA: feline.nvim has switched from famiu/feline.nvim to feline-nvim/feline.nvim
Packer failed to update feline.nvim, and I saw that it's been moved to https://github.com/feline-nvim/feline.nvim.
-
Feline.nvim switching back to rolling-release model
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.
What are some alternatives?
grapple.nvim - Neovim plugin for tagging important files
lualine.nvim - A blazing fast and easy to configure Neovim statusline written in Lua
vim-afterglow - Vim adaptation of the Afterglow colorscheme
galaxyline.nvim - neovim statusline plugin written in lua
bionic.nvim
lualine.nvim - A blazing fast and easy to configure neovim statusline plugin written in pure lua.
this-week-in-neovim-contents - Contents of weekly news delivered by this-week-in-neovim.org.
vim-code-dark - Dark color scheme for Vim and vim-airline, inspired by Dark+ in Visual Studio Code
easyread.nvim - bionic-like reading inside Neovim
lualine.nvim - A blazing fast and easy to configure neovim statusline plugin written in pure lua. [Moved to: https://github.com/nvim-lualine/lualine.nvim]
windline.nvim - Animation statusline, floating window statusline. Use lua + luv make some wind
nvim-dap - Debug Adapter Protocol client implementation for Neovim