Yeah, looks like it's not possible yet: github.com/zed-industri...
That's quite a bizarre choice to not support that 🤔
@marcoroth.dev
Full-Stack Web Developer • OSS Contributor • Electronic Music Addict • Ruby/Rails, JavaScript/Stimulus, Crystal • Hotwire Contributors Team • StimulusReflex Core. Website: marcoroth.dev Building: rubyevents.org | rubyconferences.org | gem.sh | hotwire.io
Yeah, looks like it's not possible yet: github.com/zed-industri...
That's quite a bizarre choice to not support that 🤔
I actually implemented that as well as I have been doing that too. But it's a separate custom block-comment request you can bind to a shortcut.
But I realized that I only have been doing that because my editor kept messing it up. I thought it would be sad to bake in that workaround into the LSP 😅
Hopefully it's Thyme-saving!
I got to work on another thing that has been bothering me for a long time: toggling comments in HTML+ERB files.
Sadly the Language Server Protocol doesn't support this with a dedicated request, but you can implement it using a custom request plus a small config in the editor.
Jira, so you get the full and real experience, obviously 🥸
I'm sure we could make something work, as Zed seems super configurable.
Maybe we can/need to bake it directly into the Zed Ruby Extension.
Maybe @vitallium.bsky.social has an idea on how to approach that 👀
Turns out the secret ingredient was Herb all along 🪄🌿
My current tooling can't even handle removing the trailing %> when uncommenting.
This is magical!! 🪄✨
At least for VS Code we can pre-configure it out of the box in the VS Code extension!
github.com/marcoroth/he...
I got to work on another thing that has been bothering me for a long time: toggling comments in HTML+ERB files.
Sadly the Language Server Protocol doesn't support this with a dedicated request, but you can implement it using a custom request plus a small config in the editor.
I really like how this new `erb-no-duplicate-branch-elements` linter rule and its autofix are shaping up!
This level of understanding, awareness, and integration still feels purely magical.
We've had a lot of issues and PRs around updates - events, new videos, changelog, and more. I tried to bring all that together in the newsletter. ♥️
Let me know what you think and if you have ideas for March! ✨
Hello friends! This is our first edition of the Ruby Events Newsletter!
Find recent events, released videos, and a changelog within. Let us know if there's anything you want to see in March's edition? 🤩
www.rubyevents.org/announcement...
I really like how this new `erb-no-duplicate-branch-elements` linter rule and its autofix are shaping up!
This level of understanding, awareness, and integration still feels purely magical.
The `textDocument/documentHighlight` request in the Language Server Protocol is kinda neat!
The Herb Language Server will use it to highlight matching ERB control flow keywords and HTML tag pairs when you place your cursor on them.
Week 07/08 - Video recorder UI, Dynamic Partial Rendering, and more!
This pull request improves the parser's error reporting for HTML close tags that are missing their closing `>` by introducing a new `UnclosedCloseTagError`. Given this input: ```html+erb <% case Date.today.cwday %> <% when 6 %> <p>Today is Saturday</p <% else %> <p>Today is not a day of the week</p> <% end %> ``` Previously, when parsing `</p` (missing closing `>`), the error was reported on the next tag (e.g., `<% else %>`) instead of on the `</p` itself. Additionally, the next token (e.g., `<%`) would get incorrectly consumed as the `tag_closing` of the `HTMLCloseTagNode`.
These kinds of small fixes are oddly satisfying to get right. This ships in the next version of Herb! 🙌
This pull request improves the parser's error reporting for HTML close tags that are missing their closing `>` by introducing a new `UnclosedCloseTagError`. Given this input: ```html+erb <% case Date.today.cwday %> <% when 6 %> <p>Today is Saturday</p <% else %> <p>Today is not a day of the week</p> <% end %> ``` Previously, when parsing `</p` (missing closing `>`), the error was reported on the next tag (e.g., `<% else %>`) instead of on the `</p` itself. Additionally, the next token (e.g., `<%`) would get incorrectly consumed as the `tag_closing` of the `HTMLCloseTagNode`.
These kinds of small fixes are oddly satisfying to get right. This ships in the next version of Herb! 🙌
Awesome, thanks for giving it a go! 🙏
Looks like you are still missing out on fish! 🙈
Yay, congrats! 😍🙌🏼
Annie Kiley How To Finish What You Start: Lessons From Actually Shipping a Big Refactor Brooke Kuhlmann Terminus: A Hanami + htmx web application for e-ink devices Christine Seeman Optimize Your Mindset (Without Overclocking) David Paluy LLM Telemetry as a First-Class Rails Concern Ifat Ribon Yes, &…: Ruby’s Secret Talent for Improvisation Joël Quenneville State is the First Decision You Never Made John Athayde Learning from Permaculture: Sustainable Software Development Kevin Murphy InstiLLMent of Successful Practices in an Agentic World Rachael Wright-Munn Your First Open-Source Contribution Thomas Cannon 5 ways to invest in yourself for the long haul
This mid-February morning, you can almost tell that spring is coming. 🌱 Today we're pleased to announce 10 wonderful Rubyists who will be bringing their stories, insights, and wisdom to the Blue Ridge stage April 30 & May 1. Hope to see you there! blueridgeruby.com
Good luck and have fun! I'm sure it's going to be great! 🚀
Week 05/06 - OAuth Bridge Components, Turbo + ActionCable Trap, and more!
I think a tighter ti.to integration might make more sense. There is so much to account for, including payments, taxes, etc.
Let's build it right into @rubyevents.org! 🙌🏼
It's been on our list for quite some time 🙈
It’s really awesome to see Mike giving back to the community in this way, especially on top of consistently supporting in-person Ruby events over the last years.
Thank you, Mike!
Super honored to be selected for the Gem Fellowship 🙏
I’ll continue pushing Herb forward as we get closer to 1.0 as part of this grant!
Announcing the winners of the 2026 Gem Fellowship! gem.coop/updates/2026...