Post #2701920
2025-02-05 23:56 UTC
@chrysn@chaos.social Can I ask you a quick follow-up question?
In an ideal world, how would you like the connection-making to work? Right now, you run :EthersyncHedgedoc in a buffer.
But maybe some automation would be more convenient, like a directory containing some config file with the HedgeDoc instance, and every time you open a file, you're automatically connected to that pad of the same name on the instance?
Or some other mechanism?
Replies (1)
-
@chrysn@chaos.social 2025-02-06 00:04
@blinry@chaos.social As a kneejerk reaction, I think `vim https://notes.ietf.org/mypd` (or `:e https:…`) should decide whether anything smarter than "GET the document and try to PUT it on writing" (which generally is a good default) is provided by plugins, probably by attempting some of the discovery options. If opening the root path behaves like a directory, even nicer. On saving, this might go into a cache (maybe ~/.cache/ethersync/by-url/notes.ietf.org/mypd), most config I'd like is changing that per host.