oceanic-next VS onedarkpro.nvim

My preferred colorscheme (https://github.com/mhartington/oceanic-next) and many others I've tried turn into a christmas tree when this happens. To the point that I have to go out of my way to disable receiving semantic tokens (it's also the main reason I don't enable treesitter based highlighting).

OceanicNext ftw

Note, I'm using (oceanic-next as colorscheme.

It's the beautiful Oceanic Next. :) https://github.com/mhartington/oceanic-next

-OceanicNext (currently use this one)

Source

Colorscheme: Oceanic-Next

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.