Hi Joe,
Bastien writes:
> See the docstring of `org-priority-highest':
I'm discarding this patch right now - feel free to submit a bug report
if there is something I missed.
Thanks,
--
Bastien
Hi Joe,
Joe Corneli via "General discussions about Org-mode."
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.,
Hi Joe,
Thanks for looking into this and figuring out a patch. I’ve just taken a peek at
your patches, and I have two minor comments:
⁃ Why use saved-position instead of save-excursion
⁃ I’m think ascii versions of ② et. al would be preferable
Also, I notice that your patches are just diffs and
Actually, there some bigger problems with the function as well...
— It didn’t update the priority cookie properly when one had been set before
* [#1] Exercise: update to [#2]
— After fixing that, I noticed that the included save-excursion doesn’t work
In the case of numeric priorities [#1] [#9] and so on, there is a test
that is reversed in org.el. This appears twice with a slight variation.
;; Are we are less than the highest or greater than the lowest?
(or (< (upcase new) org-priority-highest)
(> (upcase new) org-priority-lowest))
The
