vim-nightfly-colors VS neovim

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.

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.