From: Samuel Wales <firstname.lastname@example.org>
Subject: [BUG] priority regexp too lax. google is not an org priority cookie.
Date: Mon, 15 Mar 2021 21:59:09 -0700 [thread overview]
Message-ID: <CAJcAo8uhPWVnamykT1JC=a2rQuuaxAMvENPL9vgjcuE50MpVAw@mail.gmail.com> (raw)
(org-entry-get (point) "PRIORITY") on the following produces google.
i expected B.
> *********** REF 21:31 -ChanServ- [#google] bug
perhaps the regexp is too lax. perhaps was intended for performance.
also, mere opinion as user, i would propose the cookie just after the
todo kw as i think it was before. 3rd party packages' regexps could
prefer knowing where it is supposed to be. also pasted user text
could include false positives if the regexp is loose as it is now,
even if this case is fixed. however, perhaps this rule was relaxed
The Kafka Pandemic
Please learn what misopathy is.
reply other threads:[~2021-03-16 4:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \
* 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).