From: Firmin Martin <firmin.martin@ens-lyon.fr>
To: emacs-orgmode@gnu.org
Subject: Bug: Effort prompt write malformed input in agenda file even after reporting the error [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/local/share/emacs/26.3/lisp/org/)]
Date: Fri, 08 Nov 2019 18:06:11 +0100 [thread overview]
Message-ID: <87y2wq8fi4.fsf@ens-lyon.fr> (raw)
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.
------------------------------------------------------------------------
In the agenda buffer, I've called the `org-set-effort` function
with the `e` key, and input "-" which is malformed. I did receive
an error `Invalid duration format: "-"`, but the "-" has still been
written in the entry as an effort property.
As a consequence of this bug, opening the agenda buffer raise again
the error `Invalid duration format: "-"` which results that the agenda
buffer cannot be opened. The malformed line
:Effort: -
can only be found by a dichotomic search which is quite annoying.
For a similar issue, see here
https://emacs.stackexchange.com/questions/36111/invalid-duration-format-org-agenda/53637#53637
Maybe other functions have the same behavior (writing
malformed value on the agenda even after reporting the error).
Emacs : GNU Emacs 26.3 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.8)
of 2019-10-22
Package: Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @ /usr/local/share/emacs/26.3/lisp/org/)
next reply other threads:[~2019-11-08 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 17:06 Firmin Martin [this message]
2020-02-11 11:21 ` Bug: Effort prompt write malformed input in agenda file even after reporting the error [9.1.9 (release_9.1.9-65-g5e4542 @ /usr/local/share/emacs/26.3/lisp/org/)] Bastien
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=87y2wq8fi4.fsf@ens-lyon.fr \
--to=firmin.martin@ens-lyon.fr \
--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).