vim-nightfly-colors VS fzf.vim

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.

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

https://github.com/junegunn/fzf.vim

And added my keyboard shortcuts.

There are two plugins allowing us to use fzf in Vim: the native fzf plugin directly installed with fzf, and fzf.vim. The second plugin is built on the first one.

You might be interested in installing the fzf-vim plugin [0]. It has a user-defined command :Maps which can be used to search through all keybindings (you can also do this with just :nmap in vim, but the fzf interface is much nicer). It also provides :Commands. This behaves remarkably like VSCode's command palette.

[0] https://github.com/junegunn/fzf.vim

You'll also need https://github.com/junegunn/fzf.vim (which is imo the only vim plugin that's a must).

I do all my file operations from the command line. But to open and search files I use fzf

Regarding plugins , I am using https://github.com/Donaldttt/fuzzyy because it works in windows, unlike https://github.com/junegunn/fzf.vim

There's a :Buffers command in fzf.vim that I use extensively. It opens a fuzzy-find window with all open buffers in a MRU list.

Thanks to fzf.vim and fzf-lua, everything I learned and copied is from them.

they're likely referring to fzf.vim, the vimscript plugin from the original fzf author that wraps around fzf. there's also fzf-lua nowadays.