Open bepolymathe opened 6 months ago
Thank you for the feedback. First, I believe you are correct and that moving things around in your email app would probably break the link. I'm not entirely sure as I haven't tried it, but it would seem to make sense.
As far as a way around this, I am a little unsure how I can make my add-on interact with cb-thunderlink (i.e. how to get the proper unique base 64 string for a "cbthunderlink://SomeBase64String" URL to inject into a template). I will poke around a bit and see what I can find. If I do figure out a way, this will likely be a lower priority, optional feature so a user isn't required to have the other add-on. Sorry if this is not a fast turnaround, but I'm deep in attachment support and HTML support will take priority when that (finally!) gets done.
Regardless, thank you for reaching out to me and most of all thank you for using ObsidianClipper.
Thank you for your reply. I totally agree about the order of priorities. ObsidianClipper already brings a lot to the table.
Just to give some additional feedback on this. At least moving to a new IMAP folder (archive) doesn’t seem to break the link, it still works after for me.
Hi @KNHaw
Thanks for this wonderful plugin ! Links to the original mail created when sending to Obsidian open to a longevity problem. If I move this email to another folder, to another account folder... or to a new machine... I believe the link will no longer be functional. This is why I have been using rather than cb-thunderlink for a few years.
Experiences or feedback on this subject ?