From: Michael Powe <powem@ctpowe.net>
To: emacs-orgmode@gnu.org
Subject: Org Agenda Error
Date: Sun, 12 Jun 2022 11:48:48 -0400 [thread overview]
Message-ID: <413e82eb-db3b-8fac-7edb-35aded973dfd@ctpowe.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Hello,
Not sure if this qualifies as a bug.
This occurred when discarding an agenda item that was more than 60 days
overdue. (The repeater is 6 days.) I imagine most people take better
care of their agenda. ;-)
TODO state changed to DISCARDED
TODO state changed to TODO
[MP] Error in post-command-hook (org-add-log-note): (error "Can’t expand
minibuffer to full frame")
[MP] 10 repeater intervals were not enough to shift date past today.
Continue? (y or n) y
Entry repeats: SCHEDULED: <2022-06-16 Thu ++6d>
The two items I initialed travel together. I got this message several times.
* Org mode version 9.5.4 (release_9.5.4-535-ged6f8d.dirty @
c:/Users/micha/AppData/Roaming/.emacs.d/org-new/org-mode/lisp/)
* GNU Emacs 29.0.50 (build 2, x86_64-w64-mingw32) of 2022-06-09
Thanks.
mp
--
"Do not neglect to do good, and to share what you have." - Hebrews 13:16a
Michael Powe
Naugatuck CT USA
powem@ctpowe.net
[-- Attachment #2: Type: text/html, Size: 1437 bytes --]
next reply other threads:[~2022-06-12 15:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 15:48 Michael Powe [this message]
2022-06-12 17:46 ` Org Agenda Error Bhavin Gandhi
2022-06-13 3:29 ` Michael Powe
2022-06-13 17:31 ` Bhavin Gandhi
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=413e82eb-db3b-8fac-7edb-35aded973dfd@ctpowe.net \
--to=powem@ctpowe.net \
--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).