Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Auto-export images/markdown to vault #41

Open
glnces opened this issue Dec 20, 2024 · 4 comments
Open

Enhancement: Auto-export images/markdown to vault #41

glnces opened this issue Dec 20, 2024 · 4 comments

Comments

@glnces
Copy link

glnces commented Dec 20, 2024

Currently I sync Supernote with OneDrive. I then have a folder in my Obsidian vault that has a symlink to the notes folder synced with OneDrive so that any Supernote files are automatically pulled into my vault. I would be great if there was an option to automatically export images and/or markdown to the vault once a .note file is added. It would save a manual step!

@philips
Copy link
Owner

philips commented Dec 20, 2024

The plugin used to do this actually before I added the ability to directly view .note files.

There are a few challenges with re-introducing this, I think.

  1. In the past I scanned for files when the plugin was registered - this is not good because it can block Obsidian startup
  2. How .note file updates be handled? Does the plugin just do one conversion then stop?
  3. If .note updates are handled automatically can the timestamp be relied on across device? Maybe store a md5 or something of the .note in the markdown front matter?

@glnces
Copy link
Author

glnces commented Dec 20, 2024

Hm, these definitely add complexity.

For 2, I would do a wipe and replace for any PNG attachments for updates maybe. As for the timestamp I'm unsure if it's possible to compare the modified date of the file incoming to the file that exists since there don't seem to be any saved properties on the .note file in Obsidian.

@philips
Copy link
Owner

philips commented Jan 15, 2025

I think the way this could be accomplished is to have a property in the target markdown file. I would probably add properties like this:

---
supernote-overwrite: true
supernote-source-note-url: url
supernote-source-note-digest: sha1-aaaabbbccc 
---

@abolwell
Copy link

abolwell commented Feb 4, 2025

+1 for this feature please. Would love a way to avoid the manual step of converting new and updated notes to .md. Thank yoU!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants