Opening a file like hyper://aaj45d88g4eenu76rpmwzjiabsof1w8u6fufq6oogyhjk1ubygxy/needs-list.org
which contains
#+SETUPFILE: ./setup.org
displays the warning
Unable to read file "/tmp/setup.org"
See #188
IIUC
org-file-contents
is already capable of downloading hyperdrive file contents so long as the hyperdrive ("resource") is marked as safe. Can we refactor/extendorg--confirm-resource-safe
to handlehyper://
links/domains?
- [ ] Cause the setupfile to be read from the hyperdrive the Org file is loaded from.
- [ ] Ensure that it's done so according to security settings.
org-safe-remote-resources
was added in Org 9.6, so we may need to depend on it going forward. (And if we do that, we might want to skip to the recently released 9.7.)
Decided: We're going to require Org 9.7.3.
Item 2 above appears to be working already, but we should reverify after doing item 1.
Item 1 can probably be safely deferred until v0.5, when we add support for magic file name handlers.
See #168 for magic file name handlers / TRAMP support.
We could add a defcustom (off by default) which would add/remove
"^hyper://PUBLIC-KEY"
toorg-safe-remote-resources
when the drive is marked as safe/not unsafe.
There's WIP on
wip/org-setupfile-directives-links
branch.