emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Why is ":CLOCK => hh:mm" allowed as a clock entry?
Date: Sat, 20 Oct 2018 10:26:13 +0200	[thread overview]
Message-ID: <8736t1hvmi.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87ftx3wvyi.fsf@mbork.pl> (Marcin Borkowski's message of "Thu, 18 Oct 2018 09:33:09 +0200")

Hello,

Marcin Borkowski <mbork@mbork.pl> writes:

> I am studying the `org-clock-sum' function (I need to parse an Org file
> and extract clocking data), and I noticed that ":CLOCK => hh:mm" is
> allowed as a clock entry.  The Org syntax at
> https://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning
> confirms this.

  CLOCK:

and

  CLOCK: => hh:mm

are simply empty clocks.

> What is the rationale behind this?

Treating them as regular text would complicate parsing unnecessarily,
e.g., to determine when to stop a paragraph. 

There are other cases that can lead to odd clocks:

  CLOCK: INACTIVE-TIMESTAMP => HH:MM

where INACTIVE-TIMESTAMP is not a timestamp range.

> I want not only to sum the clocks (org-clock-sum does that, of
> course), but I want more detailed information (like how many clocks
> were that in the given period etc.). The format with only the duration
> makes this troublesome, and I'd like to ignore such entries (I have
> never seen them in my files, of course). I'm wondering what scenario
> could lead to their existence?

Hand-writing a clock information?

In any case, you can simply ignore them whenever you find them – which
shouldn't happen, right?

We can also add a checker in Org Lint for those problematic cases.

> BTW, the syntax draft says that there can be any TIMESTAMP object before
> the DURATION, but `org-clock-sum' assumes that its timestamps are
> inactive.  Isn't that a bug?

This is an oversight. Clock timestamps must be inactive. I will fix it.

Thank you.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2018-10-20  8:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  7:33 Why is ":CLOCK => hh:mm" allowed as a clock entry? Marcin Borkowski
2018-10-20  8:26 ` Nicolas Goaziou [this message]
2018-10-21 19:50   ` Marcin Borkowski

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=8736t1hvmi.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    /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

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