Can we get more examples of how we can use hyper:// and http:// protocols?

[nobiot]

@josephmturner ,

I have done my manual regression tests to prepare to bump Org-transclusion to v1.4.0 including your contributions (thank you!).

I have added a mention as a main feature in README and in the user manual.

This is not blocking v1.4, but I thought it would be great if we could get some examples for the new async methods, and transclusion over network with hyper:// and http(s)://.

Could you consider some content when you have some time?

Not blocking me bumping (I think I will do this on this weekend), though, so please take your time.

[josephmturner]

Hi @nobiot! Yes, I'm happy to add examples to the manual. I'm noticing that new async transclusion feature doesn't always play well with org-transclusion-open-source and org-transclusion-live-sync-buffers. I'll look into this tomorrow - would you be willing to hold off on releasing v1.4 a little while until these bugs are fixed?

[nobiot]

Sure, I can hold. Thank you!

[nobiot]

We may disable live-sync for asynchronous buffers, if this can be cleanly separated. Live-sync does not support all org elements so there are already some limitations.

[josephmturner]

Please see #224 for transcluding over HTTP. If we decide to merge that functionality, I'll gladly add a snippet to the manual describing its usage (in addition to a snippet describing how to transclude hyper:// content).

[josephmturner]

We may disable live-sync for asynchronous buffers, if this can be cleanly separated. Live-sync does not support all org elements so there are already some limitations.

Please see #225.

[josephmturner]

@nobiot Thank you for merging those PRs! Is the current documentation sufficient to close this issue?

[nobiot]

I haven't gotten around reading the added part (thank you for doing this!). You can move on without this issue closed, but let me keep the issue open as a reminder for myself, if you don't mind?

[josephmturner]

Sounds good.