zenbones.nvim VS onedarkpro.nvim

I use Seoulbines from https://github.com/mcchrish/zenbones.nvim I barely see it mentioned, but I love it

In neovim I favour zenbones, much preferring the subtlety of its use of bold and italic for contrast & emphasis over a mass of different (and to me distracting) colours.

I really enjoyed using https://github.com/mcchrish/zenbones.nvim it helps me to focus on your work and less distraction with colors

looking at their dotfiles it's https://github.com/mcchrish/zenbones.nvim

Zenbones' main repo. Warning: basically grayscale with minimal colors for diagnostics.

Observed that none of the colorscheme advertised at https://github.com/mcchrish/zenbones.nvim seem to be available. (The default color schemes are available, though.)

Highly recommend zenbones. Use it over a year. Besides relieving eye strain it also really helped me read and understand code better.

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.