From: David Engster <deng@randomsample.de>
To: Jan Tatarik <jan.tatarik@gmail.com>
Cc: ding@gnus.org
Subject: Re: iCalendar support: reply to invitations, sync to org
Date: Fri, 21 Jun 2013 08:56:02 +0200 [thread overview]
Message-ID: <87ip187y0t.fsf@randomsample.de> (raw)
In-Reply-To: <5n5x2rtxlbgdom.fsf@nb-jtatarik2.xing.hh> (Jan Tatarik's message of "Thu, 06 Jun 2013 22:57:29 +0200")
Jan Tatarik writes:
> I'm trying to whip it into shape for inclusion, the current effort is at
> https://github.com/jtatarik/gnus/blob/icalendar/lisp/gnus-icalendar.el
>
> It contains everything in ical-event, plus few improvements and some
> bugfixes.
Two small comments:
- The `gmm-flet' macro is not working here. I've no idea why, but I also
don't think that it matters because IMO you can just use `flet' since
it is a macro, and use
(eval-when-compile (require 'cl))
(Why do we need gmm-flet at all? It seems it was removed once already
but brought back from some reason.)
- From my experience, Gnus users do not like it at all when a mail is
send automatically without giving them a chance to look over it, even
when they just contain MIME markers. Also, like in Outlook, it would
be nice if people could still add some text to the calendar reply. So
I would remove the (mail-send-and-exit) and make it possible to
somehow edit the text/plain part. People can just hit C-c C-c when
they do not want to add/change anything.
Anyway, otherwise it's working fine. Great job.
-David
next prev parent reply other threads:[~2013-06-21 6:56 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 22:21 Jan Tatarik
2013-04-03 8:23 ` Adam Sjøgren
2013-04-03 12:38 ` Jan Tatarik
2013-04-03 15:27 ` David Engster
2013-04-03 21:28 ` Jan Tatarik
2013-04-03 22:01 ` David Engster
2013-04-03 22:52 ` Jan Tatarik
2013-06-06 15:15 ` Ted Zlatanov
2013-06-06 17:08 ` David Engster
2013-06-06 17:49 ` Ted Zlatanov
2013-06-06 18:12 ` David Engster
2013-06-06 18:17 ` Ted Zlatanov
2013-06-06 20:57 ` Jan Tatarik
2013-06-07 11:43 ` Steinar Bang
2013-06-07 12:13 ` Jan Tatarik
2013-06-07 12:41 ` Ted Zlatanov
2013-06-07 13:37 ` Steinar Bang
2013-06-21 6:56 ` David Engster [this message]
2013-08-01 15:40 ` Lars Magne Ingebrigtsen
2013-08-01 18:47 ` Jan Tatarik
2013-08-01 21:07 ` Lars Magne Ingebrigtsen
2013-08-01 21:28 ` Lars Magne Ingebrigtsen
2013-08-06 20:45 ` Jan Tatarik
2013-08-06 20:54 ` Lars Magne Ingebrigtsen
2013-08-09 22:07 ` Mats Lidell
2013-08-01 21:51 ` Jan Tatarik
2013-08-01 22:08 ` Jan Tatarik
2013-08-01 23:10 ` Lars Magne Ingebrigtsen
2013-08-01 23:26 ` Jan Tatarik
2013-08-06 20:32 ` Jan Tatarik
2013-08-06 20:36 ` Lars Magne Ingebrigtsen
2013-08-06 20:52 ` Lars Magne Ingebrigtsen
2013-08-06 21:24 ` Jan Tatarik
2013-08-12 17:32 ` Lars Magne Ingebrigtsen
2013-08-12 19:09 ` Jan Tatarik
2013-08-12 19:20 ` Lars Magne Ingebrigtsen
2013-08-02 6:20 ` Steinar Bang
2013-08-02 12:40 ` Lars Magne Ingebrigtsen
2013-08-02 13:25 ` Steinar Bang
2013-04-12 16:25 ` Eric S Fraga
2013-04-15 1:34 ` Jan Tatarik
2013-04-16 9:05 ` 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=87ip187y0t.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=jan.tatarik@gmail.com \
/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).