Tommy Jollyboat <jollyboatb...@gmail.com> writes: > However, various functions within org-mode are still using > ~string-to-char~ and giving inconsistent results, because numerical > priorities are parsed wrongly, or sometimes return nil (or #10 to > #64).
Confirmed. > * SOLUTION > > If we agree that numeric priorities should be supported everywhere, > various functions need updating: > ... Yes. > These should all be fairly safe/uncontroversial changes to make, as > any documents that are impacted were relying on undefined behavior > (such as using chars outside of the range A-Z as priorities). Not so safe. I tried to fix this specific issue in the past and changing the org-element parser to handle non-single char priorities broke tests (either because I did something stupid or because the tests make incorrect assumptions). It would be really nice if someone worked on this issue and resolved all the possible corner cases in the tests and elsewhere. We must eventually support numeric properties, as documented in the manual. -- Ihor Radchenko // yantar92, Org mode contributor, 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>
