emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Guido Stevens <guido.stevens@cosent.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Regression: org-duration fails to support duration ranges since Org 9.0.6
Date: Mon, 23 Sep 2024 14:21:21 +0200	[thread overview]
Message-ID: <d8211957-de5b-4377-9578-7d77cf62f7c3@cosent.net> (raw)
In-Reply-To: <87ed5cruis.fsf@localhost>

Thanks for looking into this, Ihor.

On 9/22/24 09:56, Ihor Radchenko wrote:
>> 2. Set estimate "1d-2d" on a task (C-c C-x e)
> 
> At this point, using emacs -Q, I am getting
> 
> Debugger entered--Lisp error: (error "Invalid duration format: \"1d-2d\"")
>    error("Invalid duration format: %S" "1d-2d")
> 
> In other words, such ranges are not supported in Effort property.
> 
> I am not sure what Doom does so that you are not getting that error.

My bad. Invalid reproduction. My local patch for org-duration-to-minutes 
must've been active when doing that, because org-duration-to-minutes is 
called by org-set-effort to validate the new input value.

> As a workaround, I suggest using some other property for your effort
> estimates. Then, est+ summary in column view will work without errors.

Thanks, I have done just that now.

-- 
     Guido Stevens    |   Cosent   |     https://cosent.nl

     s o c i a l   k n o w l e d g e   t e c h n o l o g y


      reply	other threads:[~2024-09-23 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 12:01 support range durations Guido Stevens
2024-09-15 12:02 ` Ihor Radchenko
2024-09-16  8:41   ` Guido Stevens
2024-09-22  7:56     ` [BUG] Regression: org-duration fails to support duration ranges since Org 9.0.6 (was: support range durations) Ihor Radchenko
2024-09-23 12:21       ` Guido Stevens [this message]

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=d8211957-de5b-4377-9578-7d77cf62f7c3@cosent.net \
    --to=guido.stevens@cosent.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).