[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Orgmode] Org-mode 4.78
From: |
dave |
Subject: |
Re: [Orgmode] Org-mode 4.78 |
Date: |
Wed, 20 Jun 2007 14:57:21 +0900 (JST) |
On Date: Wed, 20 Jun 2007 06:37:44 +0200, Carsten Dominik <address@hidden>
wrote:
>
> On Jun 20, 2007, at 5:06, address@hidden wrote:
>
> > On Date: Tue, 19 Jun 2007 10:56:35 +0200, Carsten Dominik
> > <address@hidden> 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
- Re: [Orgmode] Org-mode 4.78, (continued)
[Orgmode] Re: Org-mode 4.78, Michael, 2007/06/19
Re: [Orgmode] Org-mode 4.78, Juraj Kubelka, 2007/06/19
Re: [Orgmode] Org-mode 4.78, dave, 2007/06/19
Re: [Orgmode] Org-mode 4.78, Carsten Dominik, 2007/06/21
Re: [Orgmode] Org-mode 4.78, Dmitri Minaev, 2007/06/20