emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <wtd@pobox.com>
To: emacs-orgmode@gnu.org
Subject: "Cache corruption detected" when editing CLOCK timestamp by hand
Date: Fri, 22 Oct 2021 14:47:25 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2110221439160.26519@shell3.miskatonic.org> (raw)

Sometimes I edit timestamps by hand when I'm clocking things.  I had a task 
where I'd clocked in and wanted to close by hand (by adding --[2021 and so on to 
the CLOCK line) but when I started typing this popped up in a window:

Warning (emacs): org-element--cache: Cache corruption detected in work-diary.org. Resetting.
  The error was: (error #("Not an Org time string: []" 24 25 (wrap-prefix #(" 
" 0 8 (face org-indent)) line-prefix #("        " 0 8 (face org-indent)) fontified t) 25 26 (wrap-prefix #("        " 0 8 (face org-indent)) line-prefix #("        " 0 8 (face org-indent)) fontified t))) Disable showing Disable 

"[2021" certainly isn't a time string, but the warning surprised me.  I presume 
it's because of the recent improvements about persistence.  I have no 
suggestions but thought I'd point it out in case it might crop up more if other 
people enter clock timestamps by hand.



William Denton
Librarian, artist and licensed private investigator.
Toronto, Canada

             reply	other threads:[~2021-10-22 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 18:47 William Denton [this message]
2021-10-22 18:56 ` "Cache corruption detected" when editing CLOCK timestamp by hand William Denton
2021-10-23  3:34 ` Ihor Radchenko
2021-10-23  3:52   ` Ihor Radchenko
2021-11-23 12:34     ` [PATCH] " Ihor Radchenko
2022-04-30  3:37       ` Ihor Radchenko
2022-05-30 11:50       ` Ihor Radchenko
2022-10-05  4:55         ` 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:

  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=alpine.DEB.2.22.394.2110221439160.26519@shell3.miskatonic.org \
    --to=wtd@pobox.com \
    --cc=emacs-orgmode@gnu.org \


* 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).