3 ms·
I tried Zed just yesterday and sadly my experience wasn’t “just works”. It just works if you haven’t used any of the Neovim configs/distributions. But for someo
by tecoholic 2y ago
I tried Zed just yesterday and sadly my experience wasn’t “just works”. It just works if you haven’t used any of the Neovim configs/distributions. But for someone who already uses LazyVim, LunarVim..etc., it’s kind of meeting the expectations.
The issue for me was with the Docker LSP. I have a codebase where a Dockerfile is a Jinja Template. Zed’s syntax highlighting broke at the first curly braces. Both my Doom EMacs and LazyVim seem to have no problem with it. I couldn’t work beyond that point.
- magnio 2y ago> I have a codebase where a Dockerfile is a Jinja Template. Jesus
- tecoholic 2y agoTrust me. I feel the same way.
- deleted 2y ago[deleted]
- seabrookmx 2y agoIs it named Dockerfile or Dockerfile.jinja?
- tecoholic 2y agoIt’s named Dockerfile. However, I suspect if it’s named jinja, the Docker parts won’t be syntax highlighted!?!?
- seabrookmx 2y agoIn my experience, yes. But you can't really expect a syntax highlighter to support every combination of template language and file language, so this seems reasonable enough.
- tecoholic 2y agoI understand the limitation. Especially in the context of having the entire syntax tree parsed and stored like Zed. I didn’t expect it to highlight 2 languages. I just wanted the Dockefile parts to be highlighted. But Zed stopped any highlighting after the first curly brace, which produces inferior results compared to the regex (assuming) based highlighters out there.
- seabrookmx 2y agoRight but the curly brace is invalid syntax in a Dockerfile. It's valid IMO for the parser to bail when it encounters this. I see what you're saying that other highlighters are continuing gracefully though.