emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Gregor Zattler <grfz@gmx.de>
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: Tue, 31 May 2022 13:01:17 +0800	[thread overview]
Message-ID: <877d621ejm.fsf@localhost> (raw)
In-Reply-To: <87o7zfoze0.fsf@no.workgroup>

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
>
> CLOCK:
>
> 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?

Best,
Ihor


  reply	other threads:[~2022-05-31  5:01 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 [this message]
2022-06-01 15:36       ` Gregor Zattler
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=877d621ejm.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=grfz@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

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