From mboxrd@z Thu Jan 1 00:00:00 1970 From: jmcbray@carcosa.net (Jason F. McBrayer) Subject: Re: Org-mode 4.78 Date: Wed, 20 Jun 2007 09:27:21 -0400 Message-ID: References: <20070620.120646.82285502.dave@skiddlydee.com> <2143f0b939ece84eaaebe33cbf7dbea4@gmail.com> <20070620.145721.260794033.dave@skiddlydee.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I10DW-0005ty-FJ for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 09:27:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I10DU-0005tF-Mk for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 09:27:26 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I10DU-0005tA-CT for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 09:27:24 -0400 Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.33]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I10DU-0006WN-14 for emacs-orgmode@gnu.org; Wed, 20 Jun 2007 09:27:24 -0400 Received: from bertrand.carcosa.net ([24.168.217.245]) by cdptpa-omta01.mail.rr.com with ESMTP id <20070620132722.YCUK20315.cdptpa-omta01.mail.rr.com@bertrand.carcosa.net> for ; Wed, 20 Jun 2007 13:27:22 +0000 In-Reply-To: <20070620.145721.260794033.dave@skiddlydee.com> (dave@skiddlydee.com's message of "Wed\, 20 Jun 2007 14\:57\:21 +0900 \(JST\)") 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: emacs-orgmode dave@skiddlydee.com writes: > > 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. I'd like to be able to assign dates to these timestamp-less clock entries. Just to have a way of saying "I worked on this for two hours on Tuesday" without having to clock in and out specific times. Useful for entering things retroactively, for example, or putting in full-day events. -- +-----------------------------------------------------------+ | Jason F. McBrayer jmcbray@carcosa.net | | If someone conquers a thousand times a thousand others in | | battle, and someone else conquers himself, the latter one | | is the greatest of all conquerors. --- The Dhammapada |