From: Gregor Zattler <grfz@gmx.de>
To: emacs-orgmode@gnu.org
Subject: [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: Mon, 30 May 2022 12:02:49 +0200 [thread overview]
Message-ID: <8735grjq2e.fsf@no.workgroup> (raw)
Ciao,
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
Dear org mode developers, Ihor,
I accidentally inserted a "z" into a closing timestamp in a
clockline like so: 20zznn22-05-30
This happened because I use key chors and didn't enter the
chord fast enough.
This produced a *Warnings* buffer of 2,3 MB size.
Next time I provoced this it was only 66 KB *Warnings*
I use org mode as build a few weeks ago, dunno if this still
of interest.
Since the backtrace contains private information I would
rather not send it to the list, but to an individual maybe!?
If this backtraces are of interest, whom should I send them
to?
Ciao; Gregor
Emacs : GNU Emacs 29.0.50 (build 3, x86_64-pc-linux-gnu, X toolkit, cairo version 1.16.0)
of 2022-05-15
Package: Org mode version 9.5.3 (release_9.5.3-471-gebbef7.dirty @ /home/grfz/src/org-mode/lisp/)
--
Gregor
next reply other threads:[~2022-05-30 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 10:02 Gregor Zattler [this message]
2022-05-30 11:51 ` [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/)] Ihor Radchenko
2022-05-30 14:42 ` Gregor Zattler
2022-05-31 5:01 ` Ihor Radchenko
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=8735grjq2e.fsf@no.workgroup \
--to=grfz@gmx.de \
--cc=emacs-orgmode@gnu.org \
/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).