emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: emacs-orgmode@gnu.org
Subject: Are colons forbidden for TODO keywords?
Date: Wed, 2 Nov 2022 01:37:15 -0500	[thread overview]
Message-ID: <CAMg28Ove8-xwW1oi=ej2NNaGyS6YD6yxc34vBzzhqt-uCBZ1Wg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1463 bytes --]

*Am I correct that colons are forbidden for TODO keywords (at very least as
the last character)? *
I can't see an explicit prohibition in the manual, or in
https://orgmode.org/worg/dev/org-syntax.html, but I'm seeing behavior that
suggests there perhaps should be, as follows.

So, for vaguely aesthetic reasons, I decided I'd like my TODO keywords to
end in colons. That is: TODO:, INPROGRESS:, DONE:, and so on; instead of
just TODO, INPROGRESS, DONE, etc. And it seemed to work fine. At very least
for things like cycling through sequences, quick selection, color and other
face attributes, and so on, there didn't seem to be any issue.

However I've just noticed that the colons do seem to be a problem for smart
tree construction. For example, if I run 'C-c / T' and provide "DONE:"
(with colon) as the keyword, no headlines are found, despite there being
many with that keyword in the relevant file. But if I provide "DONE" (no
colon)[1] as the keyword, then all of my "DONE:" (with colon) headlines are
found.

As I say, I can't find anything in the documentation saying that colons are
forbidden, but it's beginning to feel like it. Does that sound credible, in
which case does the documentation need a tweak? Or was there no intention
to restrict colon use, in which case is it the sparse tree construction
code that needs tweaked?

thanks,
Thomas

[1] Having first added "DONE" to org-todo-keywords, so as to allow it to be
a valid choice for 'C-c / T'

[-- Attachment #2: Type: text/html, Size: 1812 bytes --]

             reply	other threads:[~2022-11-02  6:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  6:37 Tommy Kelly [this message]
2022-11-02  7:35 ` Are colons forbidden for TODO keywords? Ihor Radchenko

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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='CAMg28Ove8-xwW1oi=ej2NNaGyS6YD6yxc34vBzzhqt-uCBZ1Wg@mail.gmail.com' \
    --to=tommy.kelly@verilab.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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