all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Guido Stevens <guido.stevens@cosent.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: support range durations
Date: Sun, 15 Sep 2024 12:02:18 +0000	[thread overview]
Message-ID: <8734m1ktv9.fsf@localhost> (raw)
In-Reply-To: <ca76997e-6571-4817-8b9d-8cbf350fd1e2@cosent.net>

Guido Stevens <guido.stevens@cosent.net> writes:

> As per https://orgmode.org/manual/Column-attributes.html I'm using range 
> durations to express effort estimations. Those get summarized nicely in 
> column views, using the {est+} summarizer. But when I access an agenda 
> view that encounters a task that has such a range duration directly set, 
> the agenda chokes with an error message:
>
> 	org-duration-to-minutes: Invalid duration format: "1d-2d"

May you please provide more details on how to trigger the error?

> ...
> * lisp/org-duration.el (org-duration-to-minutes): Do not choke on
> low-high range durations (e.g. "2d-5d") when rendering an agenda. Calculate the average
> of the range instead.
>
> Range durations are valid when estimating effort, and supported
> elsewhere via the {est+} summarizer.

Org mode durations have no notion of ranges. It is completely
org-colview thing. So, modifying `org-duration-to-minutes' is not
appropriate. We need to fix org-colview, not org-duration.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-09-15 12:01 UTC|newest]

Thread overview: 3+ 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 [this message]
2024-09-16  8:41   ` Guido Stevens

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

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

  git send-email \
    --in-reply-to=8734m1ktv9.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=guido.stevens@cosent.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.