nvim VS onedark.vim

Here's mine: https://github.com/mawkler/nvim

I have quite a large config split over many files. Here's my init.lua.

Here's a link to my config.

How does this detect that it should be triggered? I have a lot of packer configuration tables moved to their own file like this:

Has anyone else had a similar issue? I can't reproduce the issue with a minimal telescope-only config, so there's likely some issue with my config. Since it happens sporadically it's very difficult to debug, so I figured I'd start by scouting the subreddit.

Link to my current config if anyone's curious.

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.

Here's my dressing.nvim config file if that's of any help.

Here's my config.

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