"Jacob S. Gordon" <[email protected]> writes: >>> You can also use numeric values for priorities >>> --8<-- >>> When using numeric priorities, you need to set >>> ~org-priority-highest~, ~org-priority-lowest~ and >>> ~org-priority-default~ to integers, which must all be a >>> non-negative integer between 0 and 64, inclusive. >>> --8<-- >>> Valid priority values are single uppercase Latin alphabetical >>> characters A-Z, and non-negative integers in between 0 and 64, >>> inclusive. > > but the doc strings of 'org-priority-highest' and > 'org-priority-lowest' are more insistent that Org either thinks about > them of numeric or alphabetic: > >>> If you set […] to a numeric value inferior to 65, Org assumes you >>> want to use digits for the priority cookie. If you set it to >=65, >>> Org assumes you want to use alphabetical characters. > > In practice, they can coexist and the values are sorted numerically > 0–64 then by character value ?A–?Z, e.g. sorting ‘Tasks’: > > #+PRIORITIES: 0 Z 45 > * Tasks > ** [#45] Middle > ** [#Z] Lowest > ** [#0] Highest > > Is this something we want to pin down?
This does not introduce bugs, right? If so, I see no reason to add constraints when we do not have to. The manual should still suggest reasonable settings, of course. -- 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>
