Thanks for catching thiis, Jacob! A small patch with unit tests is attached
that fixes the issue.

Cheers,

Derek


On Mon, Jan 5, 2026 at 1:49 PM Jacob S. Gordon <[email protected]>
wrote:

> Hey,
>
> I found one more place and some (partially existing) edge behaviour.
>
> If you enter column mode on the following header (‘C-c C-x C-c’),
> place the point on the priority column, and hit ‘S-<left>’ or
> ‘S-<right>’ it should correctly cycle through the allowed values:
>
>   #+PRIORITIES: 1 10 7
>   #+COLUMNS: %PRIORITY %ITEM
>   * Heading
>
> Attached is a small patch to ‘org-property-get-allowed-values’ that
> fixes it.
>
> The edge behaviour appears when calling ‘org-priority-up’ (‘S-<up>’)
> with point on on the priority cookie, which signals ‘Invalid priority
> value ‘-1’’ (the message is new but the error is not):
>
>   #+PRIORITIES: 0 10 5
>   * [#0] Heading
>
> With non-numeric priorities and ‘org-priority-down’ (‘S-<down>’) you
> can get a similar error (which AFAICT is a regression)
>
>   #+PRIORITIES: A Z M
>   * [#Z] Heading
>
> Thanks again for all your work on this Derek!
>
> Best,
>
> --
> Jacob S. Gordon
> [email protected]
> Please avoid sending me HTML emails and MS Office documents.
> https://useplaintext.email/#etiquette



-- 
+---------------------------------------------------------------+
| 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  |
+---------------------------------------------------------------+

Attachment: 0001-lisp-org.el-Fix-bug-when-removing-priority-due-to-wr.patch
Description: Binary data

Reply via email to