From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: clocksum bug in agenda-view with log-mode on Date: Mon, 23 Jun 2008 06:38:26 +0200 Message-ID: <16AF7387-753A-49F4-B7D0-DF04C7771E4C@uva.nl> References: <191f2a110806220700h487facd5i9ecbad1d3948703a@mail.gmail.com> <191f2a110806221802p102bb9f6kd2eb019979a4aff4@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v924) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KAdp6-0000mp-Be for emacs-orgmode@gnu.org; Mon, 23 Jun 2008 00:38:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KAdp4-0000md-HX for emacs-orgmode@gnu.org; Mon, 23 Jun 2008 00:38:35 -0400 Received: from [199.232.76.173] (port=45042 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KAdp4-0000ma-Eg for emacs-orgmode@gnu.org; Mon, 23 Jun 2008 00:38:34 -0400 Received: from ug-out-1314.google.com ([66.249.92.169]:27513) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KAdp3-0007Y4-UM for emacs-orgmode@gnu.org; Mon, 23 Jun 2008 00:38:34 -0400 Received: by ug-out-1314.google.com with SMTP id l31so346563ugc.48 for ; Sun, 22 Jun 2008 21:38:32 -0700 (PDT) In-Reply-To: <191f2a110806221802p102bb9f6kd2eb019979a4aff4@mail.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: iemacs@gmail.com Cc: org-mode mailing list On Jun 23, 2008, at 3:02 AM, iemacs@gmail.com wrote: > I tried to use Dynamic blocks and found `yesterday' doesn't work in > > #+BEGIN: clocktable :maxlevel 2 :scope file :block yesterday > > I had to use `today-1' to get it work. Fixed, thanks. - Carsten > > > On Sun, Jun 22, 2008 at 10:08 PM, Carsten Dominik > wrote: >> >> Hi Tian, >> >> yes, this is known and documented in, item 3. >> >> http://orgmode.org/manual/Agenda-column-view.html#Agenda-column-view >> >> In column view, the clocksum of an entry is treated as a single >> property >> that is >> displayed by the agenda, without limiting the time shown to the >> agenda time >> range. >> >> - Carsten >> >> On Jun 22, 2008, at 4:00 PM, iemacs@gmail.com wrote: >> >>> I'm using 6.05 currently. >>> >>> I've found a problem with the clocksum function in agenda-view with >>> log-mode. The following org file has two tasks with clock-time >>> events: >>> >>> #+COLUMNS: %25ITEM(Task) %CLOCKSUM >>> * TODO task1 >>> :CLOCK: >>> CLOCK: [2008-06-21 Sat 15:37]--[2008-06-21 Sat 16:37] => 1:00 >>> CLOCK: [2008-06-22 Sun 19:37]--[2008-06-22 Sun 20:37] => 1:00 >>> :END: >>> * TODO task2 >>> :CLOCK: >>> CLOCK: [2008-06-22 Sun 18:00]--[2008-06-22 Sun 19:00] => 1:00 >>> CLOCK: [2008-06-22 Sun 21:00]--[2008-06-22 Sun 22:00] => 1:00 >>> :END: >>> >>> In the Agenda-View, the clocksum include more clock-time event for >>> calculation, and it doesn't limit the calculation to the specific >>> day in >>> agenda-view. It shows like this: >>> >>> Task | CLOC | >>> Day-agenda (W25): >>> Sunday 22 June 2008 | 6:00 | >>> TODO task2 | 2:00 | >>> TODO task1 | 2:00 | >>> TODO task2 | 2:00 | >>> >>> >>> -- >>> Kind regards, >>> >>> Tian Qiu >>> >>> >>> _______________________________________________ >>> Emacs-orgmode mailing list >>> Remember: use `Reply All' to send replies to the list. >>> Emacs-orgmode@gnu.org >>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode >> >> > > > > -- > Kind regards, > > Tian Qiu