From: Luna Schwalbe Date: Tue, 02 Jun 2026 08:15:15 GMT Subject: Re: [PATCH] doc: document and test `@` prefix for raw timestamps Message-ID: <2194e42a-5c41-44e1-ba36-1599cbd41415@luna.gl> In-Reply-To: > Does this "additional paragraph" format correctly, instead of > rendered as a literal block (typically typeset in typewriter font, > monospace)? Don't you need to do something like what is done for > "ISO 8601::" that appears later in the same file? I.e. lose the > four-space indent and replace the blank line before it with a single > '+' list continuation operator? Terribly sorry, you're right of course, I somehow forgot to actually build and check the docs. Will send an updated patch right away. > This is totally outside the scope of this topic, but we might want > to enhance the rule a bit to declare this is *not* ambigous. As > there is no 99th month or 99th day, this cannot be in the YYYYMMDD > date format. I agree there is room for change with this rule, although I'm not sure how sensible it is to start allowing certain values based on whether they are also a valid calendar date or not (we'd end up trying to parse YYYYMMDD first, and only afterwards do the actual timestamp parsing; I feel like this might just make the system less predictable for users in practice). As far as I can tell the rule is technically not necessary at all (apart from some unusual approxidate interpretations like the `2000 +0000` example, which I honestly think are more confusing than useful), seeing that YYYYMMDD isn't a supported format anywhere. If we want to have it as a safeguard tho, better documentation is probably the most important aspect. As a user, ideally I'd love to get a "ambiguous date format, prefix with @ if you intend to specify a raw timestamp" kind of error message, but I suspect that might be difficult to implement.