From: Jan Tatarik <jan.tatarik@gmail.com>
To: ding@gnus.org
Subject: Re: gnus-icalendar - RSVP handling
Date: Tue, 19 Nov 2013 14:15:22 +0100 [thread overview]
Message-ID: <87ob5g1qj9.fsf@nb-jtatarik2.xing.hh> (raw)
In-Reply-To: <87bo1gprq7.fsf@topper.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Tue, 19 Nov 2013 12:15:44 +0100")
On Tue, Nov 19 2013, Adam Sjøgren wrote:
> 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?
Not sure about this one. Imagine receiving a forwarded invitation, sent
to you FYI. You will not be on the participant list, and definitely
should not be able to respond to it.
I would go with extending the gnus-icalendar-identities variable, which
is used to identify you on the participant list. Currently it looks at
your mail addresses only:
#+BEGIN_SRC elisp
(defvar gnus-icalendar-identities
(apply #'append
(mapcar (lambda (x) (if (listp x) x (list x)))
(list user-full-name (regexp-quote user-mail-address)
; NOTE: this one can be a list
gnus-ignored-from-addresses))))
#+END_SRC
If we let the user specify a list of mailing lists he's subscribed to
(or suck this info directly from gnus groups), we could add it to
gnus-icalendar-identities and any RSVP sent to your mailing list will
produce answer buttons for you.
Is it OK?
next prev parent reply other threads:[~2013-11-19 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:15 Adam Sjøgren
2013-11-19 13:15 ` Jan Tatarik [this message]
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=87ob5g1qj9.fsf@nb-jtatarik2.xing.hh \
--to=jan.tatarik@gmail.com \
--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).