Thanks Ihor. This library looks pretty involved so I don't think I want to reproduce a worse version of it in my code. I'll just stick to org-element-parse-buffer for now.

On a related note, what is the difference between a greater block and a lesser block according to the Org syntax spec? They seem identical in form and function to me.

In reply to @karthink:matrix.org

Thanks Ihor. This library looks pretty involved so I don't think I want to reproduce a worse version of it in my code. I'll just stick to org-element-parse-buffer for now.

On a related note, what is the difference between a greater block and a lesser block according to the Org syntax spec? They seem identical in form and function to me.

In reply to @karthink:matrix.org
Yes but that function seems to require some machinery provided by the rest of the feature, involving hash tables of regexps. At a glance it looks like I'll have to end up replicating a big chunk of it.

In reply to @yantar92:matrix.org
I can see `round` in there. Immidiately suspicious

Hello from the future. Not only have I figured this silly problem out, but it's nearly packaged for anyone else.

This is regarding a clock table and adding up "billable" hours for an invoice. I did indeed have rounding errors, and eliminated them by restructuring the org tables and entries and doing the division/multiplication once per row and summing up the table total with those values. I only end up rounding once.

You probably don't remember this but it's finally an itch I've scratched.

I've encountered the following warning/error:

Warning (org-element): org-element--cache: Org parser error in 20250312.org::416663. 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).

The code I ran which caused it was this:

  (defun sort-by-timestamp (&optional arg)
    (interactive "P")
    (mark-whole-buffer)
    (org-sort-entries
     nil (if arg ?F ?f)
     (lambda (&optional pos)
       (org-time-string-to-time
        (org-entry-get pos "TIMESTAMP")))
     (function time-less-p))
    ;; Remove extra newlines added between headlines
    (goto-char (point-min))
    (while (re-search-forward "\n\\{2,\\}\\*" nil t)
      (replace-match "\n\n*")))

What I ended up doing was to wrap the sort call in a let block, and bound org-element-use-cache to nil.

Seems to have worked.

How does the element cache work, and what are its main benefits?

I mean in general, I assume that when calling org-sort-entries or org-map-entries to do some heavy lifting then it makes sense to disable it? Or did I overlook something?

In reply to @dadinn:matrix.org
The code I ran which caused it was this: ``` (defun sort-by-timestamp (&optional arg) (interactive "P") (mark-whole-buffer) (org-sort-entries nil (if arg ?F ?f) (lambda (&optional pos) (org-time-string-to-time (org-entry-get pos "TIMESTAMP"))) (function time-less-p)) ;; Remove extra newlines added between headlines (goto-char (point-min)) (while (re-search-forward "\n\\{2,\\}\\*" nil t) (replace-match "\n\n*"))) ```