From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarmo Hurri Subject: Re: recurring events with different notes for each occurrence Date: Fri, 11 Oct 2013 19:27:13 +0300 Message-ID: <87mwmfai3i.fsf@syk.fi> References: <87y567epyv.fsf@syk.fi> <2013-10-05T17-40-36@devnull.Karl-Voit.at> <87a9imisir.fsf@syk.fi> <2013-10-06T13-31-31@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35937) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VUfYq-0001z9-Ha for emacs-orgmode@gnu.org; Fri, 11 Oct 2013 12:27:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VUfYk-00063e-MR for emacs-orgmode@gnu.org; Fri, 11 Oct 2013 12:27:32 -0400 Received: from plane.gmane.org ([80.91.229.3]:42610) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VUfYk-00063W-Gx for emacs-orgmode@gnu.org; Fri, 11 Oct 2013 12:27:26 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VUfYh-0001Mk-I8 for emacs-orgmode@gnu.org; Fri, 11 Oct 2013 18:27:23 +0200 Received: from host-137-163-18-130.edu.hel.fi ([137.163.18.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Oct 2013 18:27:23 +0200 Received: from jarmo.hurri by host-137-163-18-130.edu.hel.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 11 Oct 2013 18:27:23 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Karl Voit writes: > As a programmer, I do understand your objection. However, I tend to > have following structure: > > * Events > ** LUGG meetings :LUGG:common:tags: > > - common information about this event > > *** <...> single occurrence > *** <...> another occurrence > [...] > > For other purposes, I am also using the following approach: > > * Events > ** LUGG meetings :LUGG:common:tags: > > - common information about this event > > - <2013-09-30 Sun 18:00-20:00> > - <2013-10-06 Sun 18:00-20:00> > - [...] I tried to play with these, but did not get the extra info in the agenda. Maybe I need to get better acquainted with agendas. Is there a way to associate a property with each repeating timestamp and show this property in the agenda? (There most likely is.) Jarmo