vim-nightfly-colors VS dotfiles

nightfly

With the recent release of Neovim 0.9, now is right time for my themes moonfly and nightfly to fully embrace Lua and the native Neovim Lua API.

I just added support for LSP semantic tokens to my two themes: moonfly and nightfly.

My own theme, nightfly.

I am trying to install https://github.com/bluz71/vim-nightfly-colors. Iinstalled nightfly using packer.Whenever I set colorscheme to nightfly it defaults to the regular colors. This does not happen with any of the colorschemes that I have installed and additionally I can change to the colorscheme manually from commandline mode.

A nice minor milestone reached today; both my colorschemes, moonfly and nightfly now have exactly 500 GitHub stars each.

As a long time fzf/fzf.vim user the syntax highlighting old by bat for previewing has always irked me. I have used bat's base16 theme which kind-of works ok, but it was still not great when I use my moonfly and nightfly colorschemes. I decided to go down the rabbit hole and do something to somewhat remedy the situation. The fly16 bat theme is the result. Basically it is a derivation of bat's base16 but with colors shifted around to better integrate with moonfly & nightfly, especially when using fzf.vim with previewing enabled (which will use bat if it is installed). Installation instructions are at the repo link above. Note, bat fundamentally uses a Rust'ized version of Sublime's syntax highlighting engine with TextMate grammar, hence, there will not be a perfect match between bat highlighting and Vim/Neovim highlighting. However, I have done tweaks here and there that narrow the difference to within an acceptable range. Some of you may be wondering, why not just use telescope which will actually use Neovim itself ‏‏‎ for previewing. A couple reasons (for me): - I am lazy - I really like fzf - I sometimes use Vim, and fzf.vim works in both Neovim and Vim, whilst Telescope is Neovim only - I use fzf in the command line, hence I also like using it in Neovim as well Cheers

Hello, maintainer of moonfly and nightfly color-schemes speaking.

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 have never used lsp-zero nor mason. I crafted my own LSP setup from back in the Neovim 0.5 days, see config here if interested.

Very simple, as noted here

My Diagnostic config: https://github.com/bluz71/dotfiles/blob/master/nvim/after/plugin/diagnostic.lua

My Neovim dotfiles.

init.lua and nvim directory

Most of mine is in Vimscript except for any modern Neovim plugin, I configure all of those in Lua. You can so I sprinkle Lua lightly within my configuration.

[Tip 3] Do not use the vim-rails plugin, it really slows down startup A LOT. I have switched over to Tim Pope's other project navigation plugin projectionist which can be configured to provide most of the functionality of vim-rails (but not all). For those interested here are my projectionist mappings. The stuff I miss out on, such as opening view files under the cursor just via :Eview, I can live without.

You can look around my dotfiles to get a feel for this hybrid Neovim / Vim compatibility mode.

This is what it looks like for me and this is my indent-blankline configuration, the most important of which is this: