From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: gnus-icalendar - RSVP handling
Date: Tue, 19 Nov 2013 12:15:44 +0100 [thread overview]
Message-ID: <87bo1gprq7.fsf@topper.koldfront.dk> (raw)
Hi.
gnus-icalendar gives you Accept, Tentative, Decline-buttons if you are
an attendee and RSVP is true.
I just got an invitation addressed to a mailinglist.
So, no buttons, but an expectation from the sender that I Accept (or
Decline).
Maybe I should get the buttons by default if I am not in the list of
attendees?
Like so:
diff --git a/lisp/gnus-icalendar.el b/lisp/gnus-icalendar.el
index a827763..0a5c380 100644
--- a/lisp/gnus-icalendar.el
+++ b/lisp/gnus-icalendar.el
@@ -200,8 +200,9 @@
:organizer organizer
:start-time
(gnus-icalendar-event--decode-datefield event
'DTSTART)
:end-time (gnus-icalendar-event--decode-datefield
event 'DTEND)
- :rsvp (string= (plist-get (cadr attendee) 'RSVP)
- "TRUE")
+ :rsvp (if attendee
+ (string= (plist-get (cadr attendee) 'RSVP) "TRUE")
+ t)
:participation-required (string= (plist-get (cadr
attendee) 'ROLE)
"REQ-PARTICIPANT")
:req-participants (cdar attendee-names)
This could perhaps be improved by falling back to checking if _any_
attendee has RSVP true, and if so show buttons to press (we can't know
which of the invited mailing lists I was in, but at least one of the
mailing lists was asked to answer, so be safe and assume I am on that
list).
What do you think?
Best regards,
Adam
--
"I hope you're not going to ask me Adam Sjøgren
To explain a title." asjo@koldfront.dk
next reply other threads:[~2013-11-19 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:15 Adam Sjøgren [this message]
2013-11-19 13:15 ` Jan Tatarik
2013-11-19 21:33 ` Adam Sjøgren
2013-11-19 23:00 ` Jan Tatarik
2013-11-21 22:43 ` Adam Sjøgren
2013-12-02 15:52 ` Adam Sjøgren
2013-12-02 21:19 ` Jan Tatarik
2013-12-18 21:11 ` Adam Sjøgren
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=87bo1gprq7.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).