From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: cschr <cschr@freenet.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: individual alerts
Date: Fri, 15 Jan 2016 07:36:24 +0000 [thread overview]
Message-ID: <87r3hjxpjb.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAPTQUCgk2KtFltqvR2fA1zrCgAAAEAAAANLMA7jJ53lPsci8XqlU6oEBAAAAAA==@freenet.de> (cschr@freenet.de's message of "Tue, 12 Jan 2016 14:49:50 +0100")
On Tuesday, 12 Jan 2016 at 14:49, cschr wrote:
[...]
> I found out already how to export SCHEDULED and DEADLINE timestamps from
> orgmode to iCalendar VEVENTs, but the VALARM TRIGGERs produced always have
> the same value (VALARM TRIGGER is always “P0DT0H0M0S”). How can I define an
> individual alert for each appointment in ORGMODE, and have the alert values
> exported as icalendar VALARM TRIGGERs?
>
> The :APPT_WARNTIME: property in orgmode seems to do nothing, nor does it
> seem to help if I add a “WARNTIME …” text to the orgmode item – this seems
> to work for emacs diary entries only.
I cannot help you with the desire to have different alerts for each
appointment but I can point you to org-icalendar-alarm-time for the
actual warning time which applies to all items exported. The default is
indeed no warning but I have
(setq org-icalendar-alarm-time 10)
to give me 10 minutes' warning.
In any case, I also wanted to note that appointments should not have
scheduled and/or deadline information, just active time stamps. TODO
items, on the other hand, could/should have scheduling information. In
other words, an appointment can be as simple as:
* Meet with Joe and Martha
<2016-01-15 Fri 11:00-12:00>
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.3-449-gd85ff3
prev parent reply other threads:[~2016-01-15 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 13:49 individual alerts cschr
2016-01-13 5:30 ` Nick Dokos
2016-01-13 18:17 ` Nick Dokos
2016-01-15 7:23 ` Eric S Fraga
2016-01-15 7:36 ` Eric S Fraga [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3hjxpjb.fsf@delle7240.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=cschr@freenet.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.