2025-02-05 22:33 UTC
Replies (6)
-
@blinry@chaos.social 2026-05-06 19:53
I'm trying to get the @teamtype@fosstodon.org โ @hedgedoc@fosstodon.org bridge into a publishable state this week, to allow you to edit HedgeDoc documents using editors like Neovim and VS Code! I could use your help to decide which HedgeDoc versions we should support: Could you go to the main page of your favorite HedgeDoc instance, scroll to the bottom, and check which release is linked from the "Source Code" link? ๐ (If you use multiple instances, feel free to check for all of them, the poll is multiple-choice.)
-
@ljrk@todon.eu 2025-02-05 22:34
@blinry@chaos.social @hedgedoc@fosstodon.org @ethersync@fosstodon.org OMG, yes, very much! Especially since HedgeDoc 2.0 lacks vim support right now 0:-)
-
@chrysn@chaos.social 2025-02-05 23:01
@blinry@chaos.social @hedgedoc@fosstodon.org @ethersync@fosstodon.org This would be super useful. All note taking that happens at #IETF happens in hedgedoc, and while it's nice that it works for everyone, I keep fighting the editor's behavior. Replacing that fighting with muscle memory attuned to my trusty .vimrc would free up valuable brain cycles of those who sketch protocols live while talking.
-
@schrottkatze@social.nekover.se 2025-02-05 23:19
@blinry@chaos.social @hedgedoc@fosstodon.org @ethersync@fosstodon.org how does this work? is it LS based (read: could be adapted for helix) or sth else?
-
@kronn@ruby.social 2025-02-06 06:04
@blinry@chaos.social @hedgedoc@fosstodon.org @ethersync@fosstodon.org This seems awesome. Like many others this is/was on my personal list of things I want to see getting better in the world.
-
@tuxflo@chaos.social 2025-02-06 07:30
@blinry@chaos.social @hedgedoc@fosstodon.org @ethersync@fosstodon.org YES! Would be useful and interesting to me.