emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Markus Heller <hellerm2@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Scheduling of 2-day events
Date: Wed, 18 Nov 2009 15:11:45 -0500	[thread overview]
Message-ID: <87vdh7sida.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <he1hm3$5h0$1@ger.gmane.org> (Markus Heller's message of "Wed\, 18 Nov 2009 11\:24\:51 -0800")

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.

-Bernt

  reply	other threads:[~2009-11-18 20:11 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 [this message]
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

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=87vdh7sida.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=hellerm2@gmail.com \
    /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).