-
Notifications
You must be signed in to change notification settings - Fork 19
Description
Hi,
First off, thanks for your work on this great plugin!
I’ve run into an issue when working with .note files stored inside a symlinked folder within my Obsidian vault. Here’s a quick breakdown:
• Obsidian (official site version, not sandboxed) successfully follows the symlink — Markdown files inside the symlinked folder are visible and editable.
• However, Supernote plugin does not open .note files in that same symlinked folder.
• If I place .note files directly inside the vault (not via symlink), they are and opened as expected.
This suggests that the plugin might not be handling symlinked paths properly when scanning for .note files.
Why this matters:
Using symlinks allows users to keep .note files in a central location (e.g., synced via Supernote’s system) without duplicating or moving them. This makes for a much cleaner and more flexible workflow, especially when sharing files between Supernote and Obsidian (I'm using a folder in Dropbox for my syncing setup).
Request:
Could symlink support be added as Obsidian itself does for regular Markdown files?
Happy to help test any changes if needed.
Thanks again!