I took a look at the ox-icalendar handling of priority and I think that the current approach should handle both numeric and alphabetic priorities because it already treats everything as a number (converted to a normalized range).
I also looked at `org-context' and I've attached a patch to fix its handling of double-digit numeric priorities. After this I'm going to start looking at priority handling in `org-agenda-fontify-properties'. Cheers, Derek On Thu, Feb 19, 2026 at 8:17 AM Jacob S. Gordon <[email protected]> wrote: > On 2026-02-06 14:52, Ihor Radchenko wrote: > > Multiple #+PRIORITY keywords, just like multiple #+TODO keywords, > > will lead to undefined behavior. Org will only respect one of the > > keywords in the file. You do not need to worry about this on the > > individual exporter level. > > This probably still doesn’t move the needle, but for posterity it can > happen with a single ‘#+PRIORITY’ keyword, it just has to disagree > with the user settings: > > ;; init.el > (setopt org-priority-highest 1 > org-priority-default 5 > org-priority-lowest 10) > > # main.org > #+OPTIONS: pri:t > #+PRIORITIES: 1 3 2 > #+INCLUDE: included.org > * TODO [#2] Task > > # included.org > * TODO [#5] Task > > Best, > > -- > Jacob S. Gordon > [email protected] > Please don’t send me HTML emails or MS Office/Apple iWork documents. > https://useplaintext.email/#etiquette > https://www.fsf.org/campaigns/opendocument > -- +---------------------------------------------------------------+ | 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 | +---------------------------------------------------------------+
0001-org.el-Fix-parsing-of-numeric-priorities-for-org-con.patch
Description: Binary data
