fantasque-sans VS onedark.vim

I like it a lot! Definitely in the camp of “comic sans is over-hated for poor reasons, and might even have legibility benefits for dyslexia”, and I considered a few comic sans inspired monospaced fonts before settling on Source Code Pro. The leaders were Fantasque (https://github.com/belluzj/fantasque-sans/) and Comic Code (https://tosche.net/fonts/comic-code). (Comic Code’s creator actually links to the font you linked, Comic Mono, as an example of a free font with the same spirit!)

Ultimately I found that anything descended from or inspired by comic sans ended up a little too busy for my eyes.

If paying for a font isn't your thing but you're curious this is a free version I used to use of a similar idea. https://github.com/belluzj/fantasque-sans

For Emacs I use Fantasque Sans Mono, which has a slashed zero and some other good features (e.g. clear difference between 1 and l).

I thought it would be silly or I would hate it, but the comic sans like nature of Fantasque Sans Mono really surprised me and worked well for coding/IDE use (especially in Python): https://github.com/belluzj/fantasque-sans

I know you didn't ask but I have mild dyslexia and a friend turned me on to the font he uses for coding called Fantasque Sans. I found it to be pleasantly readable like Comic Sans without being as stylistically offensive.

Fantasque Sans (https://github.com/belluzj/fantasque-sans) - I love it and use it for years in all editors! For terminal I use a patched variant of Ubuntu Mono.

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