The method works well with the Obsidian Advanced URI community plugin (even when called outside of Obsidian, through Siri Shortcuts), which can target files at heading and block level as well.
Special characters in the full URL need to be double encoded, except for the space character (%20 is fine).
Files not present in the currently open vault can be called with the Obsidian Shortcut Launcher plugin from within Obsidian as well (you initiate the Siri Shortcut from within as you’d do normally with a share sheet). As I said, the easiest is to have these subvaults named A, B, C, etc., which will act as Vaultnames.
- Single capital letters in initial position are easy to parse in the Shortcuts app and easy to move en masse (regex
[A-Z]) with A-Shell.
I have now successfully set up a work environment where I can access any file (at any heading or block) in my main vault and not worry about Obsidian hogging too much RAM or exiting on me.
Another tip:
The [[Files#Headings]] (or blocks with ID’s) can be put into a custom dictionary of the Various Complements plugin (with as many aliases as you like as well!), which is really handy with finding otherwise elusive text blocks.
- Run regexes on your vault in Notepad++, copy the results of your links with headings, run some regex replacements to equip your full links complete with headings and copy the results to a txt file you specify as your custom dictionary in VC.