Vitaly Slobodin
@vitallium.bsky.social
Thank you! I really appreciate that!
November 27, 2025 at 12:40 PM
Thank you! I really appreciate that!
Happy to hear your thoughts on the Ruby language support. Feel free to raise an issue at github.com/zed-extensio... or just complain here :)
GitHub - zed-extensions/ruby: The Ruby language support for Zed editor
The Ruby language support for Zed editor. Contribute to zed-extensions/ruby development by creating an account on GitHub.
github.com
November 17, 2025 at 8:50 PM
Happy to hear your thoughts on the Ruby language support. Feel free to raise an issue at github.com/zed-extensio... or just complain here :)
Yeah, this seems like the best way to go.
November 11, 2025 at 3:24 PM
Yeah, this seems like the best way to go.
IMO, an extension should not provide any snippet because snippets are too opinionated.
November 11, 2025 at 12:05 PM
IMO, an extension should not provide any snippet because snippets are too opinionated.
We can only remove them as part of the extension, unfortunately. I think that should be reported to upstream: have a better way over controlling snippets.
November 11, 2025 at 12:04 PM
We can only remove them as part of the extension, unfortunately. I think that should be reported to upstream: have a better way over controlling snippets.
This grammar can parse multi-line Ruby blocks :-)
October 27, 2025 at 7:45 PM
This grammar can parse multi-line Ruby blocks :-)
Oh, wow. Thanks! Appreciate that!
August 21, 2025 at 6:14 AM
Oh, wow. Thanks! Appreciate that!
I'm with you on that. That's why I went a bit crazy and created a tree-sitter grammar for HAML (github.com/vitallium/tr...). Then @davidcornu.com created a Zed extension for it - github.com/davidcornu/z.... After all that, I now think HAML isn't a great choice as a template engine.
GitHub - davidcornu/zed-haml: Haml template syntax support for Zed
Haml template syntax support for Zed. Contribute to davidcornu/zed-haml development by creating an account on GitHub.
github.com
June 28, 2025 at 9:08 AM
I'm with you on that. That's why I went a bit crazy and created a tree-sitter grammar for HAML (github.com/vitallium/tr...). Then @davidcornu.com created a Zed extension for it - github.com/davidcornu/z.... After all that, I now think HAML isn't a great choice as a template engine.
>Happy vide coding!
Yeah. I wanted to write 'vibe,' but my spellchecker had other plans - it turned my good vibes into something less vibing.
Yeah. I wanted to write 'vibe,' but my spellchecker had other plans - it turned my good vibes into something less vibing.
June 27, 2025 at 6:49 PM
>Happy vide coding!
Yeah. I wanted to write 'vibe,' but my spellchecker had other plans - it turned my good vibes into something less vibing.
Yeah. I wanted to write 'vibe,' but my spellchecker had other plans - it turned my good vibes into something less vibing.
You can find the full changelog here github.com/zed-extensio...
Release v0.10.0 · zed-extensions/ruby
What's Changed
Update Rust crate zed_extension_api to 0.6.0 by @renovate in #108
Debugger prototype for Ruby by @osiewicz in #96
feat(herb): add Herb LSP by @vitallium in #110
Update herb-language...
github.com
June 27, 2025 at 5:07 AM
You can find the full changelog here github.com/zed-extensio...
I think that can rephrased as: in pull mode the editor knows when it needs diagnostics and asks the server for them. This approach is more efficient.
June 12, 2025 at 6:48 AM
I think that can rephrased as: in pull mode the editor knows when it needs diagnostics and asks the server for them. This approach is more efficient.
Additionally, RuboCop runs in push mode, which can be slow for large files and projects. Pull mode updates diagnostics only when they’re needed. For example, when you save a file or when you create a new file.
June 12, 2025 at 6:47 AM
Additionally, RuboCop runs in push mode, which can be slow for large files and projects. Pull mode updates diagnostics only when they’re needed. For example, when you save a file or when you create a new file.