Yes, I plan on tackling those next. To recap, what I can find in this thread is:
Functions that use string-to-char to parse: - org-entry-put - org-mobile-edit (in org-mobile.el) - org-agenda-fontify-priorities (org-agenda.el) - org-mouse-context-menu (org-mouse.el) The Org Element API also needs updating: - ~org-element--headline-parse-title~ implements its own org-priority-regexp, which doesn't account for multiple characters - ~org-entry-put~ has bugs, but I don't understand the code well enough - A couple of functions format priorities as "[#%c]", and should include a %s case for values under 65. * `org-entry-properties' assumes regexp/string that may need fixing * `org-latex-format-headline-default-function' assumes "%c" formatting * `org-element-property' makes some assumptions that may need addressed It's been a fairly long thread, but I think that covers all of the items. Did I miss any? Cheers, Derek On Sun, Nov 23, 2025 at 5:45 AM Ihor Radchenko <[email protected]> wrote: > Derek Chen-Becker <[email protected]> writes: > > > Doh! Thanks for fixing that :) > > Note that the issues reported at the beginning of this thread still do > exist. > > -- > Ihor Radchenko // yantar92, > Org mode maintainer, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> > -- +---------------------------------------------------------------+ | Derek Chen-Becker | | GPG Key available at https://keybase.io/dchenbecker and | | https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org | | Fngrprnt: EB8A 6480 F0A3 C8EB C1E7 7F42 AFC5 AFEE 96E4 6ACC | +---------------------------------------------------------------+
