Thanks for your response.
Line 855 is just a blank line in the middle of the following section:
8<-----
** DONE Respond better to HEAD methods
CLOSED: [2024-11-13 Wed 13:58]
- State "DONE" from "TOPROD" [2024-11-13 Wed 13:58]
- State "TOPROD" from "TOREV" [2024-11-13 Wed 12:19]
At very least we could put a "backstop" at the end saying
StatusMethodNotAllowed, so that people would know it's not
implemented, not not present.
ACTUALLY, turns out the golang http route matcher already interprets
"GET" as "GET or HEAD", and already does something sensible if the
request type was HEAD.
<--- [Line 855 here, empty]
So just s/"GET"/"GET, HEAD"/g; will do the trick.
--->8
Not at all clear how that blank line could cause the error described. Unless
it's trying to interpret the "code snippet" on the following line?
Thanks,
-George
----- Original message -----
From: David Masterson <dsmaster...@icloud.com>
To: George Dunlap <g...@laleolanguage.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Org parser error [9.7.11 (release_9.7.11 @
/usr/local/Cellar/emacs/30.1/share/emacs/30.1/lisp/org/)]
Date: Thursday, May 22, 2025 6:03 AM
"George Dunlap" <g...@laleolanguage.com> writes:
> org--warnings '("org-element--cache: Org parser error in
> todos.org::855. Resetting.\n The error was: (wrong-type-argument
> integer-or-marker-p nil)\n Backtrace:\nnil\n Please report this to Org
> mode mailing list (M-x org-submit-bug-report).")
Is this the error you mean? Have you looked at line 855 of todos.org?
--
David Masterson
George Dunlap
Founder, Laleo Language Limited <https://www.laleolanguage.com>
<https://www.laleolanguage.com>
