Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I've been using w0ng/vim-hybrid as my colorscheme for 8 years and I really like it. Recently I've been trying to embrace Neovim rather than treating it as a "Vim + terminal / debugger". During that journey, I downloaded nvim-treesitter and was frankly underwhelmed by its syntax highlighting. I see potential so I'd love to make it work but I'm having trouble pinning down where the problem exactly lives. Is it treesitter's parse? vim-hybrid? Or something completely different? I was hoping for some Neovim community advice :)
I've been using w0ng/vim-hybrid as my colorscheme for 8 years and I really like it. Recently I've been trying to embrace Neovim rather than treating it as a "Vim + terminal / debugger". During that journey, I downloaded nvim-treesitter and was frankly underwhelmed by its syntax highlighting. I see potential so I'd love to make it work but I'm having trouble pinning down where the problem exactly lives. Is it treesitter's parse? vim-hybrid? Or something completely different? I was hoping for some Neovim community advice :)
I'm new to Neovim stuff so I could have gone wrong in my configuration but everything seems working. For now, I've switched to tomasiser/vim-code-dark since it supports treesitter out of box but the module mismatch issue I'd mentioned is still in vim-code-dark and every other colorscheme I've tried. Is this a treesitter bug? Any advice would be appreciated