Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
tokyonight.nvim
🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I decided recently to finally break the linkage between my colorscheme and the statusline plugin. Now it is colorscheme agnostic, hence the rename to mistfly-statusline. My own two colorschemes (noted above) have explicit styling, whilst all other colorschemes will fallback to reasonable defaults. So whether one uses gruvbox, or everforest or tokyonight, mistfly-statusline will adapt accordingly.
Maintainer of moonfly and nightfly colorschemes speaking. For a while I have also maintained a simple moonfly-flavoured statusline, previously named moonfly-statusline, now renamed to mistfly-statusline.
Maintainer of moonfly and nightfly colorschemes speaking. For a while I have also maintained a simple moonfly-flavoured statusline, previously named moonfly-statusline, now renamed to mistfly-statusline.
Maintainer of moonfly and nightfly colorschemes speaking. For a while I have also maintained a simple moonfly-flavoured statusline, previously named moonfly-statusline, now renamed to mistfly-statusline.
I decided recently to finally break the linkage between my colorscheme and the statusline plugin. Now it is colorscheme agnostic, hence the rename to mistfly-statusline. My own two colorschemes (noted above) have explicit styling, whilst all other colorschemes will fallback to reasonable defaults. So whether one uses gruvbox, or everforest or tokyonight, mistfly-statusline will adapt accordingly.
I decided recently to finally break the linkage between my colorscheme and the statusline plugin. Now it is colorscheme agnostic, hence the rename to mistfly-statusline. My own two colorschemes (noted above) have explicit styling, whilst all other colorschemes will fallback to reasonable defaults. So whether one uses gruvbox, or everforest or tokyonight, mistfly-statusline will adapt accordingly.
I already use a statusline plugin such or lightline or Lualine, should I change? Answer: no
I already use a statusline plugin such or lightline or Lualine, should I change? Answer: no
Related posts
- Change statusLine design
- Neovide Lags. Should I do something in order to prevent it . Or it's just how it is....
- nvim-linefly - Just what the world needs, yet another Lua statusline plugin (I'm sorry)
- Show me your statusline! Big plus if you wrote it yourself :)
- which statusline plugin are you using?