You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating and maintaining this much-needed plugin. Unfortunately, I am unable to use it because of the requirement that the source path must be relative to the vault's root. (In other words, it's an absolute path from the vault's perspective.)
I would rather like to set the path relative to the current note.
For example, if my note's attachments reside in folder files below the current folder, the source: value should be files/table.csv (or maybe ./files/table.csv, to distinguish it from paths relative to the vault's root).
Reason:
With a path relative to the vault's root, if I move the note and its attachment folder to another folder, the source path breaks.
A path relative to the current note would survive any note rearrangements, as long as the relative path to the note's attachments does not change.
The text was updated successfully, but these errors were encountered:
Repository owner
locked and limited conversation to collaborators
Mar 1, 2023
Hi,
Thanks for creating and maintaining this much-needed plugin. Unfortunately, I am unable to use it because of the requirement that the source path must be relative to the vault's root. (In other words, it's an absolute path from the vault's perspective.)
I would rather like to set the path relative to the current note.
For example, if my note's attachments reside in folder
files
below the current folder, thesource:
value should befiles/table.csv
(or maybe./files/table.csv
, to distinguish it from paths relative to the vault's root).Reason:
With a path relative to the vault's root, if I move the note and its attachment folder to another folder, the
source
path breaks.A path relative to the current note would survive any note rearrangements, as long as the relative path to the note's attachments does not change.
The text was updated successfully, but these errors were encountered: