emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Headline with 2 timestamps is displayed only once in the agenda
Date: Tue, 21 Apr 2009 11:38:19 +0200	[thread overview]
Message-ID: <C2C9322F-1600-4F8A-8DD8-F637BE6D12E1@gmail.com> (raw)
In-Reply-To: <87ljpu2xb5.fsf@thinkpad.tsdh.de>


On Apr 21, 2009, at 11:03 AM, Tassilo Horn wrote:

> Hi all,
>
> I have this entry in an org-file.
>
> --8<---------------cut here---------------start------------->8---
> ** Übung Grundlagen der Softwaretechnik (B 016)        :teaching:
>   <2009-04-22 Wed 08:30-10:00 +1w>
>   <2009-04-29 Wed 10:15-11:45> (Für Hannes übernehmen)
> --8<---------------cut here---------------end--------------->8---
>
> I expect it to be displayed every wednesday after 2009-04-22 for
> 08:30-10:00 and on 2009-04-29 it should be displayed twice: one at the
> usual time and one for 10:15-11:45.
>
> But the agenda shows only the regular entry (08:30-10:00) and omitts  
> the
> exception.  If I reorder the timestamps, so that the exception comes
> first, only the exception will be shown on 2009-04-29.  Every other
> wednesday shows the regular repeater date.
>
> What do I have to do to make that entry showing up twice on 29th  
> April?


Make the second one a SCHEDULED time stamp, for example.
When Org collects entries for the day, it goes through
the files, once for plain time stamps, once for scheduled,
once for deadlines.  When an entry matches, it stops
looking for timestamps in the same entry.  So you need
to make the stamps of different kind to make them show
up both.

> BTW: Is it possible to specify an end date for repeating events?

No, except if you use a diary sexp in the time stamp.  But not with
native Org syntax.

- Carsten

> Currently I just deactivate timestamps when they're obsolete, but
> sometimes I'd like to check which appointments I had some month ago.
>
> Bye,
> Tassilo
>
>
>
> _______________________________________________
> 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

  reply	other threads:[~2009-04-21  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  9:03 Headline with 2 timestamps is displayed only once in the agenda Tassilo Horn
2009-04-21  9:38 ` Carsten Dominik [this message]
2009-04-21 16:00   ` Tassilo Horn
2009-04-22  8:34     ` Carsten Dominik
2009-04-22  8:47       ` Tassilo Horn
2009-04-22 19:21       ` Bernt Hansen
2009-04-22 20:09         ` Carsten Dominik
2009-04-22 20:16           ` Tassilo Horn
2009-04-22 20:25             ` Carsten Dominik
2009-04-22 22:02               ` Bernt Hansen

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=C2C9322F-1600-4F8A-8DD8-F637BE6D12E1@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tassilo@member.fsf.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).