From mboxrd@z Thu Jan 1 00:00:00 1970 From: lukasz.stelmach@iem.pw.edu.pl (=?utf-8?Q?=C5=81ukasz?= Stelmach) Subject: Re: Scheduling of 2-day events Date: Mon, 23 Nov 2009 21:37:09 +0100 Message-ID: <87skc50yh6.fsf@dasa3.iem.pw.edu.pl> References: <87vdh7sida.fsf@gollum.intra.norang.ca> <87r5rvsb8f.fsf@gollum.intra.norang.ca> <87ws1mr6gm.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NCfen-0005Wq-A3 for emacs-orgmode@gnu.org; Mon, 23 Nov 2009 15:37:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NCfej-0005Ug-OW for emacs-orgmode@gnu.org; Mon, 23 Nov 2009 15:37:08 -0500 Received: from [199.232.76.173] (port=53586 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NCfei-0005UU-Vg for emacs-orgmode@gnu.org; Mon, 23 Nov 2009 15:37:05 -0500 Received: from lo.gmane.org ([80.91.229.12]:48697) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NCfei-0004I5-8U for emacs-orgmode@gnu.org; Mon, 23 Nov 2009 15:37:04 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NCfef-0006Ko-O5 for emacs-orgmode@gnu.org; Mon, 23 Nov 2009 21:37:01 +0100 Received: from dasa3.iem.pw.edu.pl ([194.29.147.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Nov 2009 21:37:01 +0100 Received: from lukasz.stelmach by dasa3.iem.pw.edu.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Nov 2009 21:37:01 +0100 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@gnu.org Bernt Hansen writes: > Markus Heller writes: > >> Bernt Hansen wrote: >>> Markus Heller writes: >>> >>>> Bernt Hansen wrote: >>>>> Markus Heller writes: >>>>> >>>>>> Hello, >>>>>> >>>>>> subject says it all. Is this the appropriate way of doing scheduling >>>>>> a 2-day event (couldn't find an example in the manual): >>>>>> >>>>>> * TODO Career/Training/Courses >>>>>> ** TODO Project Management Workshop >>>>>> SCHEDULED: <2009-11-19 Thu 9:00-16:30>--<2009-11-20 Fri 9:00-16:30> >>>>>> >>>>>> >>>>>> The agenda out put (C-c a a) looks like this: >>>>>> >>>>>> Thursday 19 November 2009 >>>>>> ABC: 9:00-16:30 Scheduled: TODO Project Management Workshop >>>>>> ABC: 9:00-16:30 (1/2): TODO Project Management Workshop >>>>>> Friday 20 November 2009 >>>>>> ABC: (2/2): TODO Project Management Workshop >>>>> I would just drop the SCHEDULED: part >>>>> >>>>> ** TODO Project Management Workshop >>>>> <2009-11-19 Thu 9:00-16:30>--<2009-11-20 Fri 9:00-16:30> >>>>> >>>>> so you don't get a duplicate entry. I'd also drop the TODO since it's >>>>> scheduled for a block of time and when the time is gone it's done - >>>>> whether you mark it DONE or not. >>>> >>>> Thanks for your reply, Bernt. >>>> >>>> The TODO changes to STARTED when I clock this task in, which I do when >>>> I'm working on my preparation. I could have a sub-task for >>>> preparation and clock this, but in the end, this doesn't really matter >>>> too much to me. >>> >>> Yes mine does too - but then I just move it back to no TODO keyword and >>> keep the clock running. >>> >>> I don't normally clock in 'events', I clock in todo tasks - so if >>> there's something to do to prepare for the event I would normally stick >>> that in another task and clock that instead. >> >> Bernt, just curious, how do you bill for the time you spent at an event? >> >> My goal here is to try to catch all the time I spend on this workshop >> project'' (it's professional development so I have to bill all the >> time I spend on it) in my time table, that's why I'm clocking it. >> This should include preparation and the time I actually spend at the >> work shop. If I followed your example, I'd create a level-3 task >> (presumably) called ``Preparation'' and clock that, and the time spend >> on this task will show up in my time table. But what about the actual >> work shop? >> >> Say you were in the same situation, how would you go about this? >> Maybe a hidden org-mode gem that I haven't discovered yet? > > Hi Marcus > > Sorry if this reply is a bit late ... I just noticed your workshop is > _today_. > > I would probably create a task something like this > > ,----[ diary.org ] > | ** Project Management Workshop 09:00-16:30 > | <2009-11-19 Thu>--<2009-11-20 Fri> > | [2009-11-19 Thu 07:57] > `---- > > to record the actual booked event with time. This blocks off a time in > my calendar on the days of the event so I know I'm busy then. I created something lik this (see: <878wdx1ajo.fsf@dasa3.iem.pw.edu.pl>) -=-=-=- * Zarządzanie projektami 09:00-17:00 :POLITECHNIKA: <2009-12-02 śro >--<2009-12-03 czw > -=-=-=- but I still get the second day below the time grid. Wednesday 2 December 2009 Projekty: 9:00-17:00 (1/2): Zarządzanie projektami :POLITECHNIKA: Thursday 3 December 2009 Projekty: (2/2): Zarządzanie projektami 09:00-17:00 :POLITECHNIKA: I get the proper result when I enumerate dates -=-=-=- * Zarządzanie projektami 09:00-17:00 :POLITECHNIKA: <2009-12-02 śro> <2009-12-03 czw> -=-=-=- but this makes the recurrence counters dissappear. -- Miłego dnia, Łukasz Stelmach