This is an older blog post I came across while reading this related one on syntax highlighting:

I am sorry, but everyone is getting syntax highlighting wrong @ tonsky.me. It was posted here 3 months ago.

I think both make great points and has pushed me to into a rabbit hole of re-writing my current Nord theme into something a bit more minimal, only for me to eventually realize Nord theme with barely any syntax highlighting (mostly white text) looks very bleak and I didn’t want to spend the time to hunt all the highlight groups to make things look good, so I tried out the Alabaster theme, which the guy from the 2nd article created and I love it, feels like it really hits that middle spot between too much highlighting and not enough.

Here’s the theme I used for nvim :

https://github.com/p00f/alabaster.nvim?tab=readme-ov-file

I changed some things (matching bracket background color for visibility, comments grayed out and property names of tables should be yellow, instead green).

You can see the picture of how it looks here

  • chasteinsect@programming.devOP
    link
    fedilink
    arrow-up
    2
    ·
    24 hours ago

    Like someone said in some thread that I read awhile back : – “if I wanted rainbows, I’d code in fucking skittles” 😂

    • exussum@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      23 hours ago

      The key takeaway for me is if you’re used to it, stopping or starting is like flipping your portrait photos on a vertical axis. I’m sure if I started and stuck with it, I would get used to it. But then I’m also picky enough that when my color schemes change from job to job, or software to software, I would just get annoyed.