-
Notifications
You must be signed in to change notification settings - Fork 21
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
Change in hypothes annotation note does not re-sync #55
Comments
Because the Hightlights template use
you can delete some of them where you need to update . |
could you please clarify on how new highlights can be synced to my vault (I'm a noob)? What's the template you use? and is it that I need to use different template depending on if I want to sync new articles or new highlights for old articles that was synced before? |
@nhan000 Here it is.The point is that I delete
|
Thanks @allworldg this worked for me, it now syncs when I slash command sync deleted files(although I have to select the file and everyone is called "object Promise"?) . The other issue I now have is that it duplicates the highlights already there. Do you know a way around this? |
@paskie1234 Sorry, I have no idea. Did you use the template I provided ? Or maybe you can try to turn on this option. |
Hi I'd love to get your plugin running (such a life saver!). I cannot get later additional/ deleted annotations via hypothesis to sync after obsidian has created the initial file. I tried the above proposed solution, not sure if this was supposed to fix it. I want my notes to get updated when I change my annotations, if a previous annotation gets deleted later, I would like it to not show up in the obsidian file (If I didn't manage to finish a paper in one sitting for example, I need to add more another time). After example above, I am left with the following code:
|
Is the data supposed to be a sync? I made a change to an annotation note and the data in Obsidian did NOT change despite manual resync. Is this by design? Thank you
The text was updated successfully, but these errors were encountered: