emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@syk.fi>
To: emacs-orgmode@gnu.org
Subject: Re: recurring events with different notes for each occurrence
Date: Fri, 11 Oct 2013 19:27:13 +0300	[thread overview]
Message-ID: <87mwmfai3i.fsf@syk.fi> (raw)
In-Reply-To: 2013-10-06T13-31-31@devnull.Karl-Voit.at

Karl Voit <devnull@Karl-Voit.at> 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

  reply	other threads:[~2013-10-11 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 14:45 Hide some timestamp repetitions; timestamp property in agenda Jarmo Hurri
2013-10-05 15:48 ` recurring events with different notes for each occurrence (was: Hide some timestamp repetitions; timestamp property in agenda) Karl Voit
2013-10-06 10:49   ` recurring events with different notes for each occurrence Jarmo Hurri
2013-10-06 11:40     ` Karl Voit
2013-10-11 16:27       ` Jarmo Hurri [this message]
2013-10-12  7:42         ` Karl Voit
2013-10-13  7:16           ` Jarmo Hurri
2013-10-06  9:35 ` Hide some timestamp repetitions; timestamp property in agenda Suvayu Ali
2013-10-06 10:37   ` Jarmo Hurri

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=87mwmfai3i.fsf@syk.fi \
    --to=jarmo.hurri@syk.fi \
    --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).