From mboxrd@z Thu Jan 1 00:00:00 1970 From: dave@skiddlydee.com Subject: Re: Org-mode 4.78 Date: Wed, 20 Jun 2007 14:57:21 +0900 (JST) Message-ID: <20070620.145721.260794033.dave@skiddlydee.com> References: <20070620.120646.82285502.dave@skiddlydee.com> <2143f0b939ece84eaaebe33cbf7dbea4@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I0tBP-0006H5-8c for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 01:56:47 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I0tBM-0006Gt-JW for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 01:56:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0tBM-0006Gq-EY for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 01:56:44 -0400 Received: from newsometer.com ([128.121.51.168]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1I0tBL-0000KR-Ef for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 01:56:43 -0400 In-Reply-To: <2143f0b939ece84eaaebe33cbf7dbea4@gmail.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: carsten.dominik@gmail.com Cc: emacs-orgmode@gnu.org On Date: Wed, 20 Jun 2007 06:37:44 +0200, Carsten Dominik wrote: > > On Jun 20, 2007, at 5:06, dave@skiddlydee.com wrote: > > > On Date: Tue, 19 Jun 2007 10:56:35 +0200, Carsten Dominik > > wrote: > >> - 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. Got it. Thanks, it's working for me now. > > 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. Sorry, that was pretty vague. What I meant was, if you have a clock table like this: #+BEGIN: clocktable :maxlevel 4 :emphasize nil :block lastweek ... the ":block lastweek" part doesn't really fit with clock entries like ** some entry CLOCK: => 2:00 since there isn't any date info in the clock entry. It appears that these entries are included in the clock table no matter what the setting of :block or :tstart, :tend. This works OK for me. I can limit the table to dateless clock entries by setting :tstart to a date in the future, for example. //Dave