Thanks Jacob,
I browsed the bug reports, and it seems like this one may already
capturing the issue:
https://list.orgmode.org/orgmode/candzv_n394tymy30-kueqv+ez0fekm4gsjtrkutdvik_-dk...@mail.gmail.com/
Sorry for not checking earlier, this is my first message here and as I
understand, reported bugs on this list somewhat automatically end up on
https://updates.orgmode.org. If there is any action still pending,
please let me know.
Cheers, Lars
Am 04.06.25 um 06:20 schrieb Jacob S. Gordon:
Hey Lars,
On 2025-06-03 09:19, Lars Frantzen wrote:
Is this a bug?
I believe it is. Tracing the function calls, when the priority is
explicitly set on a heading, `org-entry-properties' extracts it as a
/string/ according to `org-priority-regexp'. Otherwise, the default
priority is taken as a /character/ and converted to a string:
#+CAPTION: `lisp/org.el/org-entry-properties'
#+begin_src emacs-lisp
(push (cons "PRIORITY"
(if (looking-at org-priority-regexp)
(match-string-no-properties 2)
(char-to-string org-priority-default)))
props)
#+end_src
This is why the default renders correctly for characters, but not
integers (your value of 7 is getting converted to a bell control
character escaped as "^G").
Thanks,
--
https://larsfrantzen.space
