From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: etc/GNUS-NEWS not updated for two years
Date: Wed, 15 Oct 2014 15:23:37 +0100 [thread overview]
Message-ID: <87h9z5e7iu.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87d29tjv7b.fsf@randomsample.de> (David Engster's message of "Wed, 15 Oct 2014 15:53:12 +0200")
On Wednesday, 15 Oct 2014 at 15:53, David Engster wrote:
[...]
> Support for ical invites (gnus-icalendar.el).
This has indeed been a useful addition.
It makes me ask: is there any support for the opposite direction, such
as creating an ical invite from an org entry? Maybe I should ask this
on the org mailing list... but I think the key difficulty for me would
be knowing how to define automatically an invite attachment in gnus?
thanks,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-40d08c9
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)
next prev parent reply other threads:[~2014-10-15 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:05 Glenn Morris
2014-10-14 16:15 ` Glenn Morris
2014-10-15 12:09 ` Lars Magne Ingebrigtsen
2014-10-15 13:53 ` David Engster
2014-10-15 14:23 ` Eric S Fraga [this message]
2014-10-15 21:47 ` Lars Magne Ingebrigtsen
2014-10-15 21:51 ` Lars Magne Ingebrigtsen
2014-10-15 13:57 ` Adam Sjøgren
2014-10-15 21:43 ` Lars Magne Ingebrigtsen
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=87h9z5e7iu.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).