emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* [BUG] <2022-04-11 Mon 17:1-19:10> is wrongly parsed as a valid timestamp [9.5.3 (release_9.5.3-461-ga3dac4 @ /home/yantar92/.emacs.d/straight/build/org/)]
@ 2022-04-30  4:24 Ihor Radchenko
  2023-05-13 10:44 ` Ihor Radchenko
  0 siblings, 1 reply; 2+ messages in thread
From: Ihor Radchenko @ 2022-04-30  4:24 UTC (permalink / raw)
  To: emacs-orgmode

Hi,

Consider the following timestamp with a typo in starting minute:

<2022-04-11 Mon 17:1-19:10>

Running org-element-context yields a timestamp object with unexpected
properties:
(timestamp
 (:type active :raw-value "<2022-04-11 Mon 17:1-19:10>"
 :year-start 2022 :month-start 4 :day-start 11
 :hour-start nil :minute-start nil
 :year-end 2022 :month-end 4 :day-end 11
 :hour-end nil :minute-end nil
 :begin 1916 :end 1943 :post-blank 0))

Note that hour/minute values are nil.

Expected: The example timestamp is not parsed as a valid timestamp, but
rather considered a paragraph.

Best,
Ihor

Emacs  : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, cairo version 1.16.0)
 of 2022-04-24
Package: Org mode version 9.5.3 (release_9.5.3-461-ga3dac4 @ /home/yantar92/.emacs.d/straight/build/org/)


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [BUG] <2022-04-11 Mon 17:1-19:10> is wrongly parsed as a valid timestamp [9.5.3 (release_9.5.3-461-ga3dac4 @ /home/yantar92/.emacs.d/straight/build/org/)]
  2022-04-30  4:24 [BUG] <2022-04-11 Mon 17:1-19:10> is wrongly parsed as a valid timestamp [9.5.3 (release_9.5.3-461-ga3dac4 @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
@ 2023-05-13 10:44 ` Ihor Radchenko
  0 siblings, 0 replies; 2+ messages in thread
From: Ihor Radchenko @ 2023-05-13 10:44 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode

Ihor Radchenko <yantar92@gmail.com> writes:

> Consider the following timestamp with a typo in starting minute:
>
> <2022-04-11 Mon 17:1-19:10>
> ...
>
> Expected: The example timestamp is not parsed as a valid timestamp, but
> rather considered a paragraph.

Upon further thinking, I do not think that the above should be parsed as
a paragraph. We are rather permissive about extra unrecognized text in
the timestamps - it is a feature.

I, however, added a low-trust linter that reports timestamps with
unexpected extra text.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ab542a653

Handled.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-05-13 10:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-30  4:24 [BUG] <2022-04-11 Mon 17:1-19:10> is wrongly parsed as a valid timestamp [9.5.3 (release_9.5.3-461-ga3dac4 @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2023-05-13 10:44 ` Ihor Radchenko

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).