Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: info-gnus-english@gnu.org
Subject: Re: gnus-calendar / gnus-icalendar in Emacs24?
Date: Fri, 19 Dec 2014 09:04:48 +0100	[thread overview]
Message-ID: <87vbl883q7.fsf@hillenius.net> (raw)
In-Reply-To: <87mw6kh383.fsf@debian.uxu>

On 19 Dec 2014, Emanuel Berg wrote:

> Gijs Hillenius <gijs@hillenius.net> writes:
>
>> The past two days I've had a few occasions to put this to the
>> test. When someone using Lotus Notes sends me an invitation,
>> gnus-icalendar is even able to return accept responses. Yay!
>>
>> For Outlook/Exchange based invitations, I can add the meeting
>> requests, but there is no [accept] thingie.
>
> I must confess that this invitation business is brand new to Yours
> Truly. I used Outlook to send love letters as a kid but perhaps what
> was lacking even then was invitations. Can I send an invitation from
> Gnus, and how is that any different from a plain mail except for some
> repercussions in (I presume) the icalendar GUI client?

[accept] sends an automatically crafted email to the meeting host ( I
don't see it, it is a flash in the minibuffer). At the host the
information also automagically gets inserted in the meeting calender
entry. (x will attend, or x has confirmed... )




      reply	other threads:[~2014-12-19  8:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 13:38 Loris Bennett
2014-12-15 15:25 ` Emanuel Berg
2014-12-15 15:54 ` Adam Sjøgren
2014-12-15 16:03 ` Charles Philip Chan
     [not found] ` <mailman.16138.1418659474.1147.info-gnus-english@gnu.org>
2014-12-15 23:35   ` Emanuel Berg
2014-12-16  1:24     ` Charles Philip Chan
     [not found]     ` <mailman.16155.1418693129.1147.info-gnus-english@gnu.org>
2014-12-16 22:41       ` Emanuel Berg
2014-12-16 22:49         ` David Engster
2014-12-16 22:52         ` Adam Sjøgren
     [not found]         ` <mailman.16239.1418770400.1147.info-gnus-english@gnu.org>
2014-12-16 23:15           ` Emanuel Berg
2014-12-17  7:36           ` Loris Bennett
2014-12-17 11:41             ` Rasmus
2015-01-21  7:53               ` Gour
2015-01-21 21:07                 ` Rasmus
2015-01-22  7:21                   ` Gour
2015-01-22 11:16                     ` Kevin Brubeck Unhammer
2015-01-22 22:17                       ` Rasmus
     [not found]             ` <mailman.16286.1418816719.1147.info-gnus-english@gnu.org>
2014-12-17 11:50               ` Loris Bennett
2014-12-17 13:47             ` Adam Sjøgren
     [not found] ` <mailman.16136.1418658867.1147.info-gnus-english@gnu.org>
2014-12-16 10:33   ` Gijs Hillenius
2014-12-16 10:39     ` Gijs Hillenius
2014-12-16 11:41       ` Adam Sjøgren
2014-12-17 13:26         ` Adam Sjøgren
     [not found]         ` <mailman.16288.1418822799.1147.info-gnus-english@gnu.org>
2015-01-13 10:07           ` Gijs Hillenius
2014-12-16 14:41     ` Gijs Hillenius
2014-12-18 16:50   ` Gijs Hillenius
2014-12-19  0:50     ` Emanuel Berg
2014-12-19  8:04       ` Gijs Hillenius [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=87vbl883q7.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --cc=info-gnus-english@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.
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).