Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: iCalendar support: reply to invitations, sync to org
Date: Thu, 06 Jun 2013 20:12:27 +0200	[thread overview]
Message-ID: <87fvwvhzw4.fsf@randomsample.de> (raw)
In-Reply-To: <8738svt9ih.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 06 Jun 2013 13:49:10 -0400")

Ted Zlatanov writes:
> On Thu, 06 Jun 2013 19:08:14 +0200 David Engster <deng@randomsample.de> wrote: 
>
> DE> Ted Zlatanov writes:
>>> On Wed, 03 Apr 2013 17:27:19 +0200 David Engster <deng@randomsample.de> wrote: 
>>> 
> DE> Jan Tatarik writes:
>>>>> The code's available at https://github.com/jtatarik/ical-event
>>> 
> DE> Thank you for working on this. This looks very interesting.
>>> 
> DE> @Lars: This would be a valuable addition to Gnus, don't you think?
>>> 
>>> I'd be OK with that, but maybe under contrib?
>
> DE> Why not Gnus proper?
>
> iCalendar is proprietary software so I don't think support for it should
> be in the base Gnus.  Or is this a universal format?

It's RFC 5545. You're probably confusing it with Apple iCal. See

http://en.wikipedia.org/wiki/ICalendar

-David



  reply	other threads:[~2013-06-06 18:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 22:21 Jan Tatarik
2013-04-03  8:23 ` Adam Sjøgren
2013-04-03 12:38   ` Jan Tatarik
2013-04-03 15:27 ` David Engster
2013-04-03 21:28   ` Jan Tatarik
2013-04-03 22:01     ` David Engster
2013-04-03 22:52       ` Jan Tatarik
2013-06-06 15:15   ` Ted Zlatanov
2013-06-06 17:08     ` David Engster
2013-06-06 17:49       ` Ted Zlatanov
2013-06-06 18:12         ` David Engster [this message]
2013-06-06 18:17           ` Ted Zlatanov
2013-06-06 20:57             ` Jan Tatarik
2013-06-07 11:43               ` Steinar Bang
2013-06-07 12:13                 ` Jan Tatarik
2013-06-07 12:41                   ` Ted Zlatanov
2013-06-07 13:37                     ` Steinar Bang
2013-06-21  6:56               ` David Engster
2013-08-01 15:40               ` Lars Magne Ingebrigtsen
2013-08-01 18:47                 ` Jan Tatarik
2013-08-01 21:07                   ` Lars Magne Ingebrigtsen
2013-08-01 21:28                     ` Lars Magne Ingebrigtsen
2013-08-06 20:45                       ` Jan Tatarik
2013-08-06 20:54                         ` Lars Magne Ingebrigtsen
2013-08-09 22:07                       ` Mats Lidell
2013-08-01 21:51                     ` Jan Tatarik
2013-08-01 22:08                     ` Jan Tatarik
2013-08-01 23:10                       ` Lars Magne Ingebrigtsen
2013-08-01 23:26                         ` Jan Tatarik
2013-08-06 20:32                         ` Jan Tatarik
2013-08-06 20:36                           ` Lars Magne Ingebrigtsen
2013-08-06 20:52                           ` Lars Magne Ingebrigtsen
2013-08-06 21:24                             ` Jan Tatarik
2013-08-12 17:32                               ` Lars Magne Ingebrigtsen
2013-08-12 19:09                                 ` Jan Tatarik
2013-08-12 19:20                                   ` Lars Magne Ingebrigtsen
2013-08-02  6:20                     ` Steinar Bang
2013-08-02 12:40                       ` Lars Magne Ingebrigtsen
2013-08-02 13:25                         ` Steinar Bang
2013-04-12 16:25 ` Eric S Fraga
2013-04-15  1:34   ` Jan Tatarik
2013-04-16  9:05     ` 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

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

  git send-email \
    --in-reply-to=87fvwvhzw4.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).