vim-nightfly-colors VS onedark.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.

Onedark has been solid so far for me

As you can see only the langauge keywords are being highlighted but not function and variable names. I am using onedark and coc.nvim.

Github: joshdick/onedark.vim

It turns out this was an issue with my theme, onedark.vim, which was out of date due to some broken configuration somewhere. I reinstalled it with vim-plug and read the README. I learned that my terminal support truecolor, so I turned it on for onedark. That fixed the problem. There's no highlight in 256-color mode, but the highlight works fine in truecolor mode. Strange.

ful1e5/onedark.nvim is completely written in Lua which means it loads way faster. It also supports Treesitter which provides way better syntax highlighting, which dick/onedark.vim doesn't. Lastly, my favourite feature is that it allows you to override/create highlight group configs and pass to the plugin before loading the colorscheme which makes customizing highlight groups super easy (and I would guess faster as well?) compared to calling highlight a bunch of times in your config. Here's What my configuration of it looks like if you're curious.

something similar to this but I am using nvim

I know it's not strictly Linux related but I'm not sure where else to post this, sorry. I have been in the process of configuring my setup including Alacritty but the colors for it look off. I'm using the one dark color scheme but the colors in the terminal don't quite match, specifically the yellow/orange looks like a dark brown. I read here that you can check if a terminal is using truecolor by using this command:

since it doesn't work with : joshdick/onedark.vim