emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Inconsistency between code and manual: org-lowest-priority or org-priority-lowest
Date: Thu, 29 Oct 2020 19:30:18 +0100	[thread overview]
Message-ID: <fc6b2b90-1174-73b3-fcf6-8245a191d504@grinta.net> (raw)


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

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?

Thank you.


             reply	other threads:[~2020-10-29 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 18:30 Daniele Nicolodi [this message]
2020-10-30  4:57 ` Inconsistency between code and manual: org-lowest-priority or org-priority-lowest Kyle Meyer
2020-10-30 11:01   ` Daniele Nicolodi
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=fc6b2b90-1174-73b3-fcf6-8245a191d504@grinta.net \
    --to=daniele@grinta.net \
    --cc=emacs-orgmode@gnu.org \


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