emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Inconsistency between code and manual: org-lowest-priority or org-priority-lowest
Date: Fri, 30 Oct 2020 12:01:06 +0100	[thread overview]
Message-ID: <df6c4b9c-34e4-0129-88fb-d40281e9f509@grinta.net> (raw)
In-Reply-To: <87blgktior.fsf@kyleam.com>

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
>> `org-priority-default' variables. However, in the code the variables
>> names are `org-highest-priority', `org-lowest-priority' and
>> `org-default-priority'.
>> In can submit a patch with a fix. However, in a case like this, should
>> the code modified to match the documentation, or vice-versa?
> 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 when you read the manual
for the latest version but look at the code for an old one...


  reply	other threads:[~2020-10-30 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 18:30 Inconsistency between code and manual: org-lowest-priority or org-priority-lowest Daniele Nicolodi
2020-10-30  4:57 ` Kyle Meyer
2020-10-30 11:01   ` Daniele Nicolodi [this message]
2020-10-31 17:30     ` Kyle Meyer
2020-11-11  8:14       ` Bastien

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:

  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=df6c4b9c-34e4-0129-88fb-d40281e9f509@grinta.net \
    --to=daniele@grinta.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \


* 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


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).