From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Clocking without timestamp Date: Sun, 17 Jul 2016 11:37:59 +0200 Message-ID: <87wpkkhafc.fsf@saiph.selenimh> References: <877fcopibb.fsf@darkstar.example.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOiWW-0008Qo-Ah for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 05:38:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bOiWR-0004U8-9y for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 05:38:08 -0400 Received: from relay3-d.mail.gandi.net ([217.70.183.195]:37484) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bOiWR-0004Ty-30 for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 05:38:03 -0400 In-Reply-To: <877fcopibb.fsf@darkstar.example.net> (Sanel Zukan's message of "Thu, 14 Jul 2016 13:31:20 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Sanel Zukan Cc: emacs-orgmode@gnu.org Hello, Sanel Zukan writes: > I've been using org-mode 7.9.3f for quite a bit time and for clocking > with unspecified timestamp I'd use the following construct: > > * Some task > CLOCK: => 2:00 > > which was perfectly valid in this org-mode version. This syntax isn't valid. Actually it is rather unexpected that it was producing something meaningful before. CLOCK lines require at least a time-stamp. Regards, -- Nicolas Goaziou