From: Bhavin Gandhi <bhavin7392@gmail.com>
To: Michael Powe <powem@ctpowe.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org Agenda Error
Date: Mon, 13 Jun 2022 23:01:50 +0530 [thread overview]
Message-ID: <CAOn=hbcRa4qrYK85p+g1BHv4B=QnvAZs-RJ0mdLn7PMjADfDbg@mail.gmail.com> (raw)
In-Reply-To: <CAOn=hbfOhhCtxiDdc_3gJD=paKqpVdP=3ZkWP45g0viVB=br3g@mail.gmail.com>
On Sun, 12 Jun 2022 at 23:16, Bhavin Gandhi <bhavin7392@gmail.com> wrote:
> 1. emacs -Q
> 2. Create test.org with following content
>
> * TODO Repeating entry
> SCHEDULED: <2022-05-01 Mon ++2d>
>
> 3. C-c C-t on the entry, shows the above error. And shifts the scheduled
> date correctly.
When this error appears, the log note entry about state change is not
added. I found this issue for the first time when I saw the state
change log notes were missing.
If I do C-c C-t again on the same entry, we get the note.
- State "DONE" from "TODO" [2022-06-13 Mon 22:48]
This is missing when we hit the error mentioned in the first mail.
next prev parent reply other threads:[~2022-06-13 17:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 15:48 Org Agenda Error Michael Powe
2022-06-12 17:46 ` Bhavin Gandhi
2022-06-13 3:29 ` Michael Powe
2022-06-13 17:31 ` Bhavin Gandhi [this message]
2022-06-18 18:00 ` [BUG] org-auto-repeat-maybe: error "Can’t expand minibuffer to full frame" and missing log note Bhavin Gandhi
2022-07-01 2:14 ` Ihor Radchenko
2022-07-03 17:10 ` Bhavin Gandhi
2022-07-04 12:03 ` Ihor Radchenko
2022-07-10 17:23 ` Bhavin Gandhi
2022-07-11 1:57 ` Ihor Radchenko
2022-07-14 15:22 ` Bhavin Gandhi
2022-07-16 9:21 ` Ihor Radchenko
2022-07-21 18:03 ` Bhavin Gandhi
2022-07-26 11:49 ` Ihor Radchenko
2022-08-16 18:17 ` Bhavin Gandhi
2022-08-17 9:45 ` Ihor Radchenko
2022-09-01 9:48 ` Bastien Guerry
2022-09-25 18:16 ` Bhavin Gandhi
2022-09-26 12:46 ` 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='CAOn=hbcRa4qrYK85p+g1BHv4B=QnvAZs-RJ0mdLn7PMjADfDbg@mail.gmail.com' \
--to=bhavin7392@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=powem@ctpowe.net \
/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).