emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: lukasz.stelmach@iem.pw.edu.pl (Łukasz Stelmach)
To: emacs-orgmode@gnu.org
Subject: Re: Scheduling of 2-day events
Date: Mon, 23 Nov 2009 21:37:09 +0100	[thread overview]
Message-ID: <87skc50yh6.fsf@dasa3.iem.pw.edu.pl> (raw)
In-Reply-To: 87ws1mr6gm.fsf@gollum.intra.norang.ca

Bernt Hansen <bernt@norang.ca> writes:

> Markus Heller <hellerm2@gmail.com> writes:
>
>> Bernt Hansen wrote:
>>> Markus Heller <hellerm2@gmail.com> writes:
>>>
>>>> Bernt Hansen wrote:
>>>>> Markus Heller <hellerm2@gmail.com> 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

      parent reply	other threads:[~2009-11-23 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 19:24 Scheduling of 2-day events Markus Heller
2009-11-18 20:11 ` Bernt Hansen
2009-11-18 20:51   ` Markus Heller
2009-11-18 22:45     ` Bernt Hansen
2009-11-18 23:00       ` Markus Heller
2009-11-19 13:26         ` Bernt Hansen
2009-11-23 19:07           ` Markus Heller
2009-11-23 20:37           ` Łukasz Stelmach [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87skc50yh6.fsf@dasa3.iem.pw.edu.pl \
    --to=lukasz.stelmach@iem.pw.edu.pl \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).