bibnotes
bibnotes copied to clipboard
stefanopagliari
Updating Library writes into protected area
Thanks for your help with this great plugin
all my Bibnotes-generated 'notes' have a protected section called ## Personalised Section at the end of the note
I have turned on "start- save manual edits" ## Personalised Section
My understanding is that nothing below the personalised section should be edited when the library updates.
However I have some placeholder hyphens under each sub heading in this region, and with each library refresh an extra hyphen gets iteratively added.
More concerningly with one update, part of a heading in this region was pasted below this area as well
@Oblique82 sorry for responding only now but this is a busy period. The "safe" section does not prevent any material in the selected section to be changed/updated. Instead it prevents any material in that section from being over-written and deleted. The implementation is fairly tacky (I would like to find a more sophisticated approach in the future) so I have to admit that I'm not surprise that when updating the note, the plugin does not recognise that hyphens are already in there.
Would you be able to share a couple of screenshots of before/after?
sure here is a link to a video showing the sequential corruption that happens with multiple updates in the section called #Personal Section
https://res.cloudinary.com/professional-integrative-medicine/video/upload/v1646708856/Troubleshooting/Screen_Recording_2022-03-08_at_1.31.55_pm_xv56tn.mov
related to this it would be great if we could use a hidden comment to mark the protected area of a note eg %% protected-area %%
however if I try this and refresh it nukes the entire top part of the note!
@Oblique82, thank you for sending this. I will look into this but this and other bug fixes will have to wait a bit as I'm dealing with other commitments at the moment. Sorry for the delay.
@stefanopagliari This may be related to #80 . I tried the case provided by @Oblique82 and it is working fine with the latest fix.
However, it looks like the fix #80 is not included in our latest release yet. When that fix is released in next version maybe @Oblique82 can try it again and see if the problem is resolved.
Understood - thanks so much for your help! On 22 Mar 2022, 8:29 PM +1030, Stefano Pagliari @.***>, wrote:
@Oblique82, thank you for sending this. I will look into this but this and other bug fixes will have to wait a bit as I'm dealing with other commitments at the moment — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>