From: Andreas Drop <drops@mailbox.org>
To: emacs-orgmode@gnu.org
Subject: 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: Thu, 20 Aug 2020 07:59:45 +0200 [thread overview]
Message-ID: <65B913C9-8307-43F9-BA1A-D0A5DA7CFF1B@mailbox.org> (raw)
In-Reply-To: <87a6yrt3vl.fsf@mailbox.org>
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 "▶"
(setq org-stuck-projects '("project" ("▶" "NEXT") nil ""))
The 'NEXT' is used here only for validating the existence of a bug, originally it was
omitted in my config.
My projects look like this:
** ⭕ [3/4] Dame Edna :project:dame:...
** ⭕ [0/13] Example project: Garage Project :project:garage:
:PROPERTIES:
:COLUMNS: %40ITEM %8Effort(Effort){:} %60BLOCKER
:COOKIE_DATA: todo recursive
:END:
*** ⸰ Find local stores for paint
*** ⸰ Choose color for paint
*** ⸰ Buy paint
*** ⸰ Move car to nearby parking lot
*** ⸰ Remove bikes
*** ⸰ Remove stuff from shelves
*** ⸰ Remove shelves
*** ▶ Garage is empty
*** ⸰ Paint walls and floor
*** ⸰ Re-install shelves
*** ⸰ Bring back bikes into garage
*** ⸰ Bring back car into garage
*** ⸰ Celebrate and close project
Both of them contain a subheading with a todo state of "▶" which should prevent them from
showing up in the stuck projects agenda view. However, they both appear
List of stuck projects:
ops: ⭕ [3/4] Dame Edna :project:dame:
ops: ⭕ [0/13] Example project: Garage Project :project:garage:
I suspected the problem to be with the excluded todo-state beeing a
unicode symbol, so I tried to substitute it with the classical 'NEXT',
so it now showed like this:
** ⭕ [3/4] Dame Edna :project:dame:
** ⭕ [0/13] Example project: Garage Project :project:garage:
:PROPERTIES:
:COLUMNS: %40ITEM %8Effort(Effort){:} %60BLOCKER
:COOKIE_DATA: todo recursive
:END:
*** ⸰ Find local stores for paint
*** ⸰ Choose color for paint
*** ⸰ Buy paint
*** ⸰ Move car to nearby parking lot
*** ⸰ Remove bikes
*** ⸰ Remove stuff from shelves
*** ⸰ Remove shelves
*** NEXT Garage is empty
*** ⸰ Paint walls and floor
*** ⸰ Re-install shelves
*** ⸰ Bring back bikes into garage
*** ⸰ Bring back car into garage
*** ⸰ Celebrate and close project
And now the Garage project is successfully removed from the stuck
projects, because it contains a NEXT at the position of the todo
keyword, despite the fact, that NEXT is not even defined as a valid todo
keyword.
Looks like in this place there is some simple string comparison magic happening, that
can't handle unicode, instead of usage of the defined org-todo-keywords
------------------------------------------------------------------------
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 2.24.32)
of 2020-08-12
Package: Org mode version 9.3.6 (9.3.6-4-gdfa7a3-elpa @ /home/andy/.config/emacs/elpa/org-20200217/)
current state:
==============
(setq
org-todo-keywords '((sequence "⭕(p)" "⸰(t)" "▶(n)"
"⏸(w)" "|" "✔(d)" "❌(c)" "⏩(r)")
)
org-stuck-projects '("project" ("▶" "NEXT") nil "")
org-use-property-inheritance t
org-tags-exclude-from-inheritance '("crypt" "project")
org-agenda-files '("~/cloud/org/ops.org")
org-closed-keep-when-no-todo t
)
Andy Drop
next prev parent reply other threads:[~2020-08-20 6:00 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 [this message]
2020-09-04 15:57 ` Bastien
2020-09-05 4:10 ` Ihor Radchenko
2020-09-23 13:02 ` Andy Drop
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=65B913C9-8307-43F9-BA1A-D0A5DA7CFF1B@mailbox.org \
--to=drops@mailbox.org \
--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).