From: Ferdinand Pieper <fer@pie.tf>
To: ding@gnus.org
Subject: [RFC] [WIP] Creating icalendar event invitations
Date: Sat, 13 Jun 2020 12:57:17 +0200 [thread overview]
Message-ID: <87k10bp71u.fsf@ims.uni-hannover.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
Hi all,
gnus has good support to accept/decline icalendar invitations with
gnus-icalendar.el. I'm looking to extend this to also allow the
creation of new invitations from within gnus.
Below is a first rough implementation which I for now kept in a
separate file from gnus-icalendar.el, but the goal would be for
the code to also live in gnus-icalendar.el.
Most of the code is still very rough and the implementation is not
handling all cases correctly. I'm mainly sharing it now to ask you
whether this is a welcome addition to gnus-icalendar and to ask
for thoughts on the general implementation, before I spend more
time to polish the code.
How it works: The code adds functions to create RFC5545 compliant
VCALENDAR and VEVENT parts from gnus-icalendar-event objects and
also a function to create a event invitation based on the current
message buffer.
To create the gnus-icalendar-event the mail addresses in the To
header are converted to required participants, addresses in Cc are
interpreted as optional participants and the subject and message
body are added as summary and description of the event. The date
range and location have to be entered interactively for now.
Please let me know if you have any other ideas on how users could
create new events.
Next step will be to polish the code so that the basic
functionality of creating simple one-shot event invitations works
reliably.
Long term goals include handling request responses and supporting
a wider range of the RFC5545 spec.
Thanks!
[-- Attachment #2: gnus-icalendar-request.el --]
[-- Type: application/emacs-lisp, Size: 10080 bytes --]
next reply other threads:[~2020-06-14 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 10:57 Ferdinand Pieper [this message]
2020-06-15 9:39 ` Eric S Fraga
2020-06-15 11:34 ` Gijs Hillenius
2020-06-15 16:18 ` Eric Abrahamsen
2020-06-15 16:28 ` 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=87k10bp71u.fsf@ims.uni-hannover.de \
--to=fer@pie.tf \
--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).