From: Ning Yuan <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Subject: Re: [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: Sun, 21 Nov 2021 19:46:14 +0800 [thread overview]
Message-ID: <CAEavL=Woeb5tQYkUoROU9oaqtNvNo0EXJtJiEnpefDT8TdLjLA@mail.gmail.com> (raw)
Sorry, please ignore my previous report. In a fresh install of emacs,
I cannot replicate this bug in 2e99997.
On Sun, Nov 14, 2021 at 12:07 PM Ihor Radchenko <email@example.com> wrote:
> - External Email -
> Ning Yuan <firstname.lastname@example.org> writes:
> > 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.
> > ...
> > Here's how my org-todo-keywords is set:
> > (setq org-todo-keywords
> > '((sequence "TODO(t)" "|" "CANCELLED(c)" "DONE(d)")))
> Thanks for reporting!
> Can you reproduce the problem with some small example Org file that you
> can share?
Notice: This email is generated from the account of an NUS alumnus. Contents, views, and opinions therein are solely those of the sender.
prev parent reply other threads:[~2021-11-21 12:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 15:54 [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/)] Ning Yuan
2021-11-14 4:07 ` Ihor Radchenko
2021-11-21 11:46 ` Ning Yuan [this message]
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).