From: Bastien <email@example.com>
To: Andreas Drop <firstname.lastname@example.org>
Subject: Re: Bug: Unicode ORG-TODO-KEYWORDS not recognized in agenda's stuck projects [9.3.6 (9.3.6-4-gdfa7a3-elpa @ /home/andy/.config/emacs/elpa/org-20200217/)]
Date: Fri, 04 Sep 2020 17:57:10 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <65B913C9-8307-43F9-BA1A-D0A5DA7CFF1B@mailbox.org> (Andreas Drop's message of "Thu, 20 Aug 2020 07:59:45 +0200")
Andreas Drop <firstname.lastname@example.org> writes:
> I configured my org-todo-keywords in a way, that they are just single
> unicode symbols instead of the classic TODO, NEXT, WAIT, DONE,etc. This is
> done in my init.el like this:
> (setq org-todo-keywords '((sequence "⭕(p)" "⸰(t)" "▶(n)" "⏸(w)" "|" "✔(d)" "❌(c)" "⏩(r)")))
> This works perfectly, so I can advance the todo-states, choose them
> directly, and filter on them in the agenda's todo-view, even org-edna,
> which heavily relies on them works as designed.
> While trying to use GTDs approach I defined a stuck project as one
> having no next action meaning, having no subheading with a todo state of "▶"
I don't see what can go wrong with unicode symbols for TODO keywords
when listing stuck projects.
Can you find `org-agenda-list-stuck-projects' with
C-h f org-agenda-list-stuck-projects RET
Go at the end of the function and instrument it with C-u C-M-x then
list stuck projects and see where the function chokes?
Thanks for your help,
next prev parent reply other threads:[~2020-09-04 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 8:51 Bug: Unicode ORG-TODO-KEYWORDS not recognized in agenda's stuck projects [9.3.6 (9.3.6-4-gdfa7a3-elpa @ /home/andy/.config/emacs/elpa/org-20200217/)] Andy Drop
2020-08-20 5:59 ` Andreas Drop
2020-09-04 15:57 ` Bastien [this message]
2020-09-05 4:10 ` Ihor Radchenko
2020-09-23 13:02 ` Andy Drop
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).