-
Notifications
You must be signed in to change notification settings - Fork 20
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
❦❦❦ IMPORTANT NOTICE ❦❦❦ on name change #11
Comments
Hi @nobiot, thanks for your work. Best, |
Oh yes. Thank you. I'll correct it a little later. Great that your pointed me to it. Thanks again. |
@gildo How about the new image? A bit subtle but added a mark highlighting for typos. |
hi @nobiot, that's really a cool solution! |
[This notice written on 18 January 2022] Happy 2022! I have changed the name of the project and package to "Org-remark" from Org-marginalia. If you are using Org-marginalia now, there are breaking changes. This package includes the feature that automatically converts the old Org-marginalia data into the new Org-remark data. Add
This feature is designed to work automatically and transparently to you, meaning you should not have to do anything, as long as you did not customize |
❦❦❦ IMPORTANT NOTICE ❦❦❦
[This notice written on 3 January 2022]
Happy 2022!
I am finalizing the the name of the package and GitHub repo. See PR #10. It’s probably going to be ”Org-remark”. The dev/name-change branch contains all the changes pertaining to the name change along some additional features – most notably, different highlighter pen colors and capability to let you create different pens (an idea borrowed from John Kitchin’s Ov-highlight).
There will be some minor breaking changes, which I am going through right now in my own machine. I will document the ways to bridge the breakages; nothing really major and I’m also trying to make the new version as backward compatible as possible from my lessons learnt.
After the change, I will propose the package to be added to ELPA.
I would appreciate any feedback or comment via PR #10, Org-roam discourse, or direct email (probably not Slack or Reddit as I’m really not present on these media).
The text was updated successfully, but these errors were encountered: