From: Ning Yuan <ningyuan@u.nus.edu>
To: emacs-orgmode@gnu.org
Subject: [BUG] org-agenda-get-scheduled in 2e99997 ignores org-todo-keywords [9.5 (release_9.5 @ /home/ning/.emacs.d/.local/straight/build-27.1/org-mode/)]
Date: Sat, 13 Nov 2021 23:54:06 +0800 [thread overview]
Message-ID: <CAEavL=UWbRPRbSCM+083YbPgUxrs+_KsyaFs-ZmNqW1NhP6-4Q@mail.gmail.com> (raw)
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
A few days ago I updated org-mode to the latest available commit,
"9.6-??-2e99997".
After this update, tasks which were closed by my custom "CANCELLED"
keyword, defined in org-todo-keywords, appeared in my org-agenda as if
they were still open.
I believe org-agenda-get-scheduled may be the culprit, but I am not too
sure.
Reverting my org-mode version to 9.5 (stable) without any change in
configuration fixed this bug for me.
Here's how my org-todo-keywords is set:
(setq org-todo-keywords
'((sequence "TODO(t)" "|" "CANCELLED(c)" "DONE(d)")))
Sorry if this description is too vague or unhelpful --- I know very
little emacs-lisp.
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
of 2020-09-02
Package: Org mode version 9.5 (release_9.5 @
/home/ning/.emacs.d/.local/straight/build-27.1/org-mode/)
Notice: This email is generated from the account of an NUS alumnus. Contents, views, and opinions therein are solely those of the sender.
next reply other threads:[~2021-11-14 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 15:54 Ning Yuan [this message]
2021-11-14 4:07 ` [BUG] org-agenda-get-scheduled in 2e99997 ignores org-todo-keywords [9.5 (release_9.5 @ /home/ning/.emacs.d/.local/straight/build-27.1/org-mode/)] Ihor Radchenko
2021-11-21 11:46 ` Ning Yuan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEavL=UWbRPRbSCM+083YbPgUxrs+_KsyaFs-ZmNqW1NhP6-4Q@mail.gmail.com' \
--to=ningyuan@u.nus.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.