Hi Kyle,
Kyle Meyer writes:
> Daniele Nicolodi writes:
>
>> On 30/10/2020 05:57, Kyle Meyer wrote:
>
>>> The org-X-priority -> org-priority-X rename happened in v9.4, with
>>> org-X-priority names retained as aliases. So, it sounds like there are
>>> some leftover bits in the code.
>>
>> You
Daniele Nicolodi writes:
> On 30/10/2020 05:57, Kyle Meyer wrote:
>> The org-X-priority -> org-priority-X rename happened in v9.4, with
>> org-X-priority names retained as aliases. So, it sounds like there are
>> some leftover bits in the code.
>
> You are absolutely right. This is what you get
On 30/10/2020 05:57, Kyle Meyer wrote:
> Daniele Nicolodi writes:
>
>> Hello,
>>
>> I found an inconsistency between the manual and implementation: the
>> Priorities section says that the range of valid priorities can be set
>> modifying the `org-priority-highest', `org-priority-lowest' and
>>
Daniele Nicolodi writes:
> Hello,
>
> I found an inconsistency between the manual and implementation: the
> Priorities section says that the range of valid priorities can be set
> modifying the `org-priority-highest', `org-priority-lowest' and
> `org-priority-default' variables. However, in the
Hello,
I found an inconsistency between the manual and implementation: the
Priorities section says that the range of valid priorities can be set
modifying the `org-priority-highest', `org-priority-lowest' and
`org-priority-default' variables. However, in the code the variables
names are
