You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a page in my Logseq about Readwise and all the research I made around it, its name was Readwise.
I wanted to delete all my synced pages in Logseq to reimport them with a new template but it also deleted my "Readwise" page.
I guess it's because the sync notifications go in this page, which in itself is a behavior I don't like because it pollutes my own notes.
Could we prevent this behavior ? The solution I would suggest is to change the destination of the sync notifications, either with a really specific name like "Readwise_Sync_Notifications" or to let the users choose it.
Thank you !
The text was updated successfully, but these errors were encountered:
@DrizztFR I'm updating the plugin to have a setting to change the Readwise page name, for cases like yours. I hope to release the version this week, I'm also updating with more bugfixes.
@DrizztFR I'm updating the plugin to have a setting to change the Readwise page name, for cases like yours. I hope to release the version this week, I'm also updating with more bugfixes.
Hi, I still facing this problem and I didn't find out how to change the destination of the sync notifications. Can you help me with this?
Hello,
I had a page in my Logseq about Readwise and all the research I made around it, its name was Readwise.
I wanted to delete all my synced pages in Logseq to reimport them with a new template but it also deleted my "Readwise" page.
I guess it's because the sync notifications go in this page, which in itself is a behavior I don't like because it pollutes my own notes.
Could we prevent this behavior ? The solution I would suggest is to change the destination of the sync notifications, either with a really specific name like "Readwise_Sync_Notifications" or to let the users choose it.
Thank you !
The text was updated successfully, but these errors were encountered: