Feature Request: Navigate between local files via links
Any document in the local directory can be linked to from any other document. These links can be used in either the editor or preview mode to navigate to the linked document.
# File Index [Notes](~Documents/Notes.taskpaper) [Memo](~Documents/Memo.md)
There is a way to do this, but the links will only work in Editorial.
You can use the
editorial://open/URL scheme to link to a local file.
Example: Link to the "Welcome.md" file:
You can get the URL sceme for a file my adding a shortcut to the file to the bookmarks bar opening the edit view and copying the URL text.
However, it would indeed be nice if this was implemented by the app itself
I made a workflow that creates a link to the currently open file
I had considered this as a potential workaround. X-callback urls open the linked document in the editor only though.
To be honest, my intention was to use the preview window as a sort of personal wiki of all my local Editorial documents, like I currently do with Trunk Notes. I'm trying to migrate over to Editorial though and it's a hassle having to sift through a directory tree with hundreds of similarly named documents to find the one I'm looking for.
If I could create an index document with links to local files and short discriptions of each file it would make my life so much easier. It would be pretty amazing also if I could serve up individual directories and browse to them with Safari or another machine on my local network. It would be nice if Pythonista and Editorial had a separate, shared directory. I doubt apple would allow such a thing.
In any case, thanks for the reply! I may ultimately end up having to go the x-callback route.
Why not use Google Drive or Dropbox as your "separate, shared directory?"
The file index file could be hosted on Drive and you could access your index file from either Pythonista or Editorial.
You could also use Python's simple server to host the file for access on other machines.
I've actually stumbled across a temporary solution using github pages, Editorial, and Working Copy that may end up providing what I need.
Thanks for the reply!