From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Org-mode 4.78 Date: Wed, 20 Jun 2007 06:37:44 +0200 Message-ID: <2143f0b939ece84eaaebe33cbf7dbea4@gmail.com> References: <20070620.120646.82285502.dave@skiddlydee.com> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I0rx2-0000NJ-VU for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 00:37:52 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I0rwz-0000N7-AE for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 00:37:52 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0rwz-0000N4-5P for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 00:37:49 -0400 Received: from mu-out-0910.google.com ([209.85.134.185]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I0rwy-0005In-BJ for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 00:37:48 -0400 Received: by mu-out-0910.google.com with SMTP id g7so42152muf for ; Tue, 19 Jun 2007 21:37:47 -0700 (PDT) In-Reply-To: <20070620.120646.82285502.dave@skiddlydee.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: dave@skiddlydee.com Cc: emacs-orgmode@gnu.org On Jun 20, 2007, at 5:06, dave@skiddlydee.com wrote: > On Date: Tue, 19 Jun 2007 10:56:35 +0200, Carsten Dominik > wrote: >> Org-mode version 4.78 is available through Emacs CVS, and at >> >> - You may specify clocking times by hand (i.e. without >> clocking in and out) using this syntax. >> >> : CLOCK: => 2:00 > > Should these time entries be picked up for clock tables? It seems that > they > aren't. Yes they are, the syntax is ** some entry CLOCK: => 2:00 i.e. no initial colon, this was a typo in the release notes. > If so, maybe there's a bug or I'm missing something set-up wise. > Also, I > guess there would be problems with time-range blocks such as > > :block thisweek I don't understand this question. - Carsten