Thanks for the plugin, conversion quality is great.
One thing we really need: control over the folder the extracted images go to. Today it is always " attachments/" next to the note (src/main.ts, assetSink), with no setting.
Our vault convention is a fixed folder "XAttachment/" inside the note's directory (also what Obsidian's "Default location for new attachments" = "In subfolder under current folder" gives us for pasted images). With the plugin, every conversion creates a new folder that we move by hand. The bare embeds survive the move, so nothing breaks, but it is a manual step on every single file.
Request: two settings in the plugin
- "Attachments folder name": a free text, e.g. "XAttachment". Placeholders would be a nice bonus ({{note}} for the note basename, so the current "{{note}} attachments" could stay the default).
- "Attachments folder location", relative to the converted note: e.g. "same folder as the note" (a subfolder next to it, the current behaviour), a relative path like "../assets", or a vault-absolute path.
Alternatively or in addition: an option "Use Obsidian's attachment setting" that calls app.fileManager.getAvailablePathForAttachment(name, notePath), so the plugin behaves exactly like paste/drag-and-drop in Obsidian. For us that alone would already do, but the two explicit settings would cover vaults with other conventions as well.
We are evaluating the plugin for a team-wide rollout, and this is the one gap left. Happy to test a pre-release and to report back.
Thanks for the plugin, conversion quality is great.
One thing we really need: control over the folder the extracted images go to. Today it is always " attachments/" next to the note (src/main.ts, assetSink), with no setting.
Our vault convention is a fixed folder "XAttachment/" inside the note's directory (also what Obsidian's "Default location for new attachments" = "In subfolder under current folder" gives us for pasted images). With the plugin, every conversion creates a new folder that we move by hand. The bare embeds survive the move, so nothing breaks, but it is a manual step on every single file.
Request: two settings in the plugin
Alternatively or in addition: an option "Use Obsidian's attachment setting" that calls app.fileManager.getAvailablePathForAttachment(name, notePath), so the plugin behaves exactly like paste/drag-and-drop in Obsidian. For us that alone would already do, but the two explicit settings would cover vaults with other conventions as well.
We are evaluating the plugin for a team-wide rollout, and this is the one gap left. Happy to test a pre-release and to report back.