Mr. Radchenko:
Here is the result from the org-lint (Nifty trick I should probably know.):
6043 low Potentially malformed timestamp [2023-10-20 Fri 097:49].
Parsed as: [2023-10-20 Fri]
6047 low Potentially malformed timestamp [2023-10-12 Thu 10;55].
Parsed as: [2023-10-12 Thu]
6883 low Potentially malformed timestamp [2023-07-11 Mon 18:54].
Parsed as: [2023-07-11 Tue 18:54]
7065 low Potentially malformed timestamp [2024-06-03 Tue 12:18].
Parsed as: [2024-06-03 Mon 12:18]
8454 low Potentially malformed timestamp [2023-05-12 Fri
06:08]--[2023-05-12 Fri 06:25 => . Parsed as: [2023-05-12 Fri
06:08]--[2023-05-12 Fri 06:25]
9234 low Potentially malformed timestamp [2023-03-27 Mon
11:02rr-[2023-03-27 Mon 11:13] . Parsed as: [2023-03-27 Mon 11:02]
All of the above has been corrected.
But, I still could not get the problem sections to clock-in. I closed
emacs and restarted, leading to:
Warning (org-element): org-element--cache: Org parser error in
habits.org::#<marker at 568369 in habits.org>. Resetting.
The error was: (wrong-type-argument integer-or-marker-p nil)
Backtrace:
nil
Please report this to Org mode mailing list (M-x
org-submit-bug-report). Disable showing Disable logging
The "Recovery" section split into two drawers: Duration Timestamps and
"DONE" timestamps. I've removed the extra :LOGBOOK: and :END: markers.
But still get the same behavior where I get an empty :CLOCK:
When I run "org-lint" again, I get an empty "Line Trust Warning" buffer.
Same happens on the "Dog Walk" TODO
Same happens on the "Daily Writing Project" TODO.
=rk=
On 6/12/24 12:58, Ihor Radchenko wrote:
[ Adding Org mailing list back to CC to keep the bug discussion public;
I will not mention anything risky from your example file here ]
Robert Nyman <rkny...@nymantechnology.com> writes:
Please find below what happens when I toggle on debug:
Debugger entered--Lisp error: (wrong-type-argument fixnump nil)
org-clock-sum((26217 47088))
...
I only get this with a couple of sections of my habits.org file. I've
cut my config down to JUST habits.org. That is the only thing I'm
currently clocking. I used to have a tasks.org, but I'm restricting it
for debugging purposes. I'll include my habits.org file here...
The culprit is
CLOCK: [2023-06-01 Thu 21rr:07]--[2023-06-01 Thu 22:08] => 1:01
The timestamp is malformed there, which leads to error.
It is still a bug in Org mode that such problem is not handled
gracefully.
Confirmed.
Meanwhile, you can fix that timestamp and other similar problems manually.
You can run M-x org-lint and Org will find suspiciously-looking
timestamps and other potential issues in your files.
