Ihor Radchenko writes:
>> Should we consider the above CLOCK line as a valid running clock or
>> maybe it should be parsed as a paragraph?
>
> I am still leaving this question open despite applying the above patch.
> At least, we need to get the bug fixed.
I now made Org parse malformed CLOCK li
Ihor Radchenko writes:
>> Minimal reproducer:
>>
>> 1. Create an empty org file and open it
>> 2. Yank the following string: "CLOCK: [2021-10-22 Fri 10:41]--[2021]"
>> 3. M-: (org-element-at-point)
>
> The attached is tentative fix for cases like the above.
Applied onto main via 4dda0d7a8. This
Ihor Radchenko writes:
> Should we consider the above CLOCK line as a valid running clock or
> maybe it should be parsed as a paragraph?
Nicolas, do you have any comment on this? I am inclined to treat
CLOCK: [2021-10-22 Fri 10:41]--[2021]
as a paragraph, not a clock line.
Best,
Ihor
Ihor Radchenko writes:
> This looks like a bug in org-element-timestamp-parser
>
> Minimal reproducer:
>
> 1. Create an empty org file and open it
> 2. Yank the following string: "CLOCK: [2021-10-22 Fri 10:41]--[2021]"
> 3. M-: (org-element-at-point)
The attached is tentative fix for cases like
