emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <grfz@gmx.de>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element-warnings when accidentially inserting "z" into timestamp [9.5.3 (release_9.5.3-471-gebbef7.dirty @ /home/grfz/src/org-mode/lisp/)]
Date: Wed, 01 Jun 2022 17:36:07 +0200	[thread overview]
Message-ID: <87h754bdlk.fsf@no.workgroup> (raw)
In-Reply-To: <877d621ejm.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 968 bytes --]

Hi Ihor,
* Ihor Radchenko <yantar92@gmail.com> [2022-05-31; 13:01]:
> Gregor Zattler <grfz@gmx.de> writes:
>> Now I realized, that even after quitting and restarting
>> Emacs, I cannot insert a timestamp, I get the following
>> error message:
>> org-parse-time-string: Not an Org time string: [20zznn22-05-30 Mo 11:34]
>> And then there is a dangling
>> line without timestamps at the expected line in my org file.
>> It took a while till I realized that there was a corrupted
>> timestamp in my org file a few clock lines below.
>> It would be helpful, if the message contained the file name
>> and probably even the line number.
> Could you please create an example file and detail the steps how you got
> the error?

Please see the attached test.org and call Emacs like so:

/usr/local/bin/emacs-29.0.50 -Q -L ~/src/org-mode/lisp /tmp/test.org --eval '(switch-to-buffer "test.org")' -f org-clock-in

[-- Attachment #2: test.org --]
[-- Type: application/x-org, Size: 153 bytes --]

[-- Attachment #3: Type: text/plain, Size: 51 bytes --]

Thanks for looking into this.

Ciao; Gregor

  reply	other threads:[~2022-06-01 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 10:02 [BUG] org-element-warnings when accidentially inserting "z" into timestamp [9.5.3 (release_9.5.3-471-gebbef7.dirty @ /home/grfz/src/org-mode/lisp/)] Gregor Zattler
2022-05-30 11:51 ` Ihor Radchenko
2022-05-30 14:42   ` Gregor Zattler
2022-05-31  5:01     ` Ihor Radchenko
2022-06-01 15:36       ` Gregor Zattler [this message]
2022-06-03  6:04         ` [BUG, confirmed] org-clock-in calling org-clock-sum fails leaving incomplete CLOCK line when encountering existing malformed CLOCK lines Ihor Radchenko
2022-10-13  6:15           ` Ihor Radchenko
2022-10-14 18:52             ` Gregor Zattler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h754bdlk.fsf@no.workgroup \
    --to=grfz@gmx.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).