onedarkpro.nvim VS vim-nightfly-colors

Recently, I’d like to alter a theme with a new one in NeoVim. The onedarkpro is a fantastic theme that I’ve used for a long time, but it’s difficult to defeat the temptation to try out another theme like NeoSolarized.

I suspect it should be { fg = '${white}' }. That's what I do for olimorris/onedarkpro.nvim

I have some tokens applied generally, here. And i've also added specific filetype semantic tokens too. Here are TypeScript and Python ones.

Modified, One Dark Pro (love the vscode theme but the nvim plugin got some sus highlights so i modified it)

Thanks! But it's basically just OneDarkPro.nvim with a couple changes :)

I'm using onedarkpro.nvim

Might be worth checking out onedarkpro.nvim. It's based on the VS Code namesake and has a darker option. I am the author btw!

In the image above, I have my theme, OneDarkPro.nvim, with its opinionated lua filetype highlights, versus how it would look if filetype highlights were disabled:

Yes, I use onedarkpro.nvim plugin. I tried removing nvim-tree from its settings, yet still nothings changes aside from colours itself.

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.