From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: individual alerts
Date: Wed, 13 Jan 2016 13:17:45 -0500 [thread overview]
Message-ID: <87d1t57392.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 877fjem4ge.fsf@pierrot.dokosmarshall.org
Nick Dokos <ndokos@gmail.com> writes:
> "cschr" <cschr@freenet.de> writes:
>
>> Hello
>>
>> Im a software developer and new to emacs. I want to maintain my calendar appointments in
>> orgmode, and define individual alerts for each appointment (which also includes to have no
>> alert for some appointments). Using the emacs diary is not enough for me – I want orgmode!
>>
>>
>> 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.
>>
>
> There are various constraints on the item in order to get a VALARM: it
> has to be a TODO item, it has to have a timestamp with both date and
> time in it and the timestamp has to *follow* the properties drawer.
>
> I think this last one is a bug in ox-icalendar.el: when I add a
> SCHEDULED timestamp, it gets added right after the headline, pushing
> the properties drawer down, and ISTR that that is now the mandated order
> of org things, but that seems to break ox-icalendar.el's
> ability to find the timestamp.
>
> This was mostly trial-and-error (with just a look or two into the code),
> so it might be wrong.
>
> However, the following org file:
>
> * TODO foo
> :PROPERTIES:
> :APPT_WARNTIME: 10
> :END:
> SCHEDULED: <2016-01-13 Wed 12:00>
> something to do
>
> exports to a reasonable-looking ics file:
>
> ...
>
> whereas the "normal" position of the timestamp:
>
> * TODO foo
> SCHEDULED: <2016-01-13 Wed 12:00>
> :PROPERTIES:
> :APPT_WARNTIME: 10
> :END:
> something to do
>
> leads to a rather sorry-looking ics file:
>
> ...
The OP sent me a private reply, saying that he couldn't get it to work,
but he is using an old org version (whatever comes with emacs 24.3.1
IIRC, presumably pre-8.0).
I should have mentioned that I'm using fairly recent versions:
Org-mode version 8.3.3 (release_8.3.3-437-g4de71e)
on this machine and an even later one on the machine where I did the
above testing.
--
Nick
next prev parent reply other threads:[~2016-01-13 18:18 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 [this message]
2016-01-15 7:23 ` Eric S Fraga
2016-01-15 7:36 ` Eric S Fraga
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=87d1t57392.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--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).