unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulf Jasper <ulf.jasper@web.de>
To: emacs user <emacs_user@hotmail.com>
Cc: 5433@debbugs.gnu.org
Subject: bug#5433: calendar: ical export
Date: Wed, 20 Jan 2010 19:40:06 +0100	[thread overview]
Message-ID: <84pr541uyh.fsf@web.de> (raw)
In-Reply-To: <BLU109-W10E68BF03EA9D29D0D95D4F8640@phx.gbl>

emacs user <emacs_user@hotmail.com> writes:
> In GNU Emacs 23.1.91.4 (i386-apple-darwin9.8.0, NS apple-appkit-949.54) of 2010-01-16 on Windowing system distributor `Apple', version 10.3.949 configured using `configure  '--with-ns' '--without-x''
> it seems that the export of calendar to ical format does not include the exporting of alarms.  I could be wrong, but perhaps what's missing is something like
> BEGIN:VALARMX-WR-ALARMUID:C095B897-11FE-4D33-85E8-A933A67B1147ACTION:AUDIOTRIGGER:-PT15MATTACH;VALUE=URI:BassoEND:VALARM

icalendar.el ignores VALARM components during import and does not generate
them during export.

In iCalendar a VALARM is part of a VEVENT.  In Emacs the equivalent of a
VEVENT is a diary entry and the equivalent of a VALARM would be an
appointment notification. An appointment is generated (via
appt-make-list etc.) from a diary entry but it is not part of it.

icalendar import and export converts a diary file from and to an ical
file. Appointments are (currently) not involved.

There appears to be no obvious solution how to implement VALARM support.
(One could add a VALARM to each exported VEVENT scheduled 10 minutes or
so before the event. But that would be rather stupid.)

Any suggestions?

Ulf






  reply	other threads:[~2010-01-20 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 11:24 bug#5433: calendar: ical export emacs user
2010-01-20 18:40 ` Ulf Jasper [this message]
     [not found]   ` <BLU109-W3F1B323F11347DA5C18AFF8630@phx.gbl>
2010-01-21 19:39     ` Ulf Jasper
     [not found]       ` <BLU109-W28FF30672E68F51BD68E61F8630@phx.gbl>
2010-01-22 17:30         ` Ulf Jasper
2014-11-17 20:25           ` Ulf Jasper
2014-11-22 15:31             ` Ulf Jasper

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84pr541uyh.fsf@web.de \
    --to=ulf.jasper@web.de \
    --cc=5433@debbugs.gnu.org \
    --cc=emacs_user@hotmail.com \
    /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.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).