From: Bastien <bzg@gnu.org>
To: Joe Corneli via "General discussions about Org-mode."
<emacs-orgmode@gnu.org>
Cc: Joe Corneli <joseph.corneli.orgmode@hyperreal.enterprises>
Subject: Re: [patch] priorities range reversed
Date: Sun, 26 Sep 2021 15:44:09 +0200 [thread overview]
Message-ID: <87a6jz78pi.fsf@gnu.org> (raw)
In-Reply-To: <87v94ewyvw.fsf@Proteus> (Joe Corneli via's message of "Mon, 09 Aug 2021 14:06:43 +0100")
Hi Joe,
Joe Corneli via "General discussions about Org-mode."
<emacs-orgmode@gnu.org> writes:
> In the case of numeric priorities [#1] [#9] and so on, there is a test
> that is reversed in org.el.
See the docstring of `org-priority-highest':
The highest priority of TODO items.
A character like ?A, ?B, etc., or a numeric value like 1, 2, etc.
The default is the character ?A, which is 65 as a numeric value.
If you set ‘org-priority-highest’ 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 both cases, the value of ‘org-priority-highest’ must be
smaller than ‘org-priority-lowest’: for example, if "A" is the
highest priority, it is smaller than the lowest "C" priority:
65 < 67.
Are you sure the numeric value for `org-priority-highest' is smaller
than that of `org-priority-lowest'?
For numeric priorities, [#1] is always "higher" than [#2].
If I'm not wrong and if you think we can throw a more useful error
earlier to the useful, could you provide a patch for this?
Let me know if I'm missing something, thanks,
--
Bastien
next prev parent reply other threads:[~2021-09-26 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 13:06 [patch] priorities range reversed Joe Corneli via General discussions about Org-mode.
2021-08-09 13:51 ` Joe Corneli via General discussions about Org-mode.
2021-08-31 15:14 ` Timothy
2021-09-26 13:44 ` Bastien [this message]
2021-09-29 11:27 ` Bastien Guerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6jz78pi.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=joseph.corneli.orgmode@hyperreal.enterprises \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).