From: Jan Tatarik <jan.tatarik@gmail.com>
To: ding@gnus.org
Subject: Re: Gnus window configuration with transient buffers
Date: Fri, 15 Mar 2013 23:53:08 +0100 [thread overview]
Message-ID: <5n5x2rli9owa0b.fsf@nb-jtatarik2.xing.hh> (raw)
In-Reply-To: <871ubgy7nt.fsf@randomsample.de> (David Engster's message of "Fri, 15 Mar 2013 17:00:54 +0100")
On Fri, Mar 15 2013, David Engster wrote:
> Since I was already kneep-deep in the calendaring business (through
> org-caldav), I'm afraid I also started adding icalendar support to
> Gnus. I didn't publish it yet because I wanted to add the ability to
> accept/decline invitations first, but I pushed it now:
> https://github.com/dengste/gnus-icalendar
I'll have a look.
> I'd like to see your code; maybe we can work together on this, which I
> consider to be the last step to let Gnus finally reign the enterprise.
https://github.com/jtatarik/ical-event
I have no problem with merging or abandoning my code, as long as there's
code that does the job for me.
With what I have right now, you can create/update/cancel a calendar
entry in org file of your choice, just by clicking a button in the gnus
calendar buffer. The org capture template used for creating new entries
is created automatically. As long as you're OK with storing events in
one place, single click does it.
next prev parent reply other threads:[~2013-03-15 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 10:28 Jan Tatarik
2013-03-15 13:53 ` Eric S Fraga
2013-03-15 16:00 ` David Engster
2013-03-15 22:53 ` Jan Tatarik [this message]
2013-03-16 3:27 ` Dave Goldberg
2013-03-22 14:50 ` Jan Tatarik
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=5n5x2rli9owa0b.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).