From: Simon Thum <simon.thum@gmx.de>
To: aitor <aitors2005@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: ical2org.py
Date: Thu, 16 May 2013 21:41:40 +0200 [thread overview]
Message-ID: <51953674.5030402@gmx.de> (raw)
In-Reply-To: <20130515080151.GA567@sipc87.si.ehu.es>
On 05/15/2013 10:01 AM, aitor wrote:
> Hi,
>
> On Wed, May 15, 2013 at 12:56:02AM +0200, Bastien wrote:
>> Hi Simon,
>>
>> Simon Thum <simon.thum@gmx.de> writes:
>>
>>> It's going to be confusing if we add them all.
>>
>> On the contrary -- I think collecting all the information about
>> various solutions in the same place is the only way to encourage
>> comparisons, which is the best way to let one solution emerge,
>> if needed.
>
> indeed. Should I've known there were already so many implementations of
> ical2org I wouldn't have created mine! Silly thing is, it never ocurred
> to me to just search "ical2org" on google.
Similar here, I just checked Worg. However I had some special wishes
unlikely to be covered, so I was prepared to hack anyway.
I recall to have lost my worg pushability, Bastien can you check? I
would reorganize this a bit to make it clearer, and do not want to push
something just to know.
@aitor if you have some info how your impl compares let the list know.
Cheers,
Simon
next prev parent reply other threads:[~2013-05-16 19:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 10:04 ical2org.py aitor
2013-05-14 8:37 ` ical2org.py Bastien
2013-05-14 20:40 ` ical2org.py Simon Thum
2013-05-14 22:56 ` ical2org.py Bastien
2013-05-15 8:01 ` ical2org.py aitor
2013-05-16 19:41 ` Simon Thum [this message]
2013-05-16 19:47 ` ical2org.py Bastien
2013-05-21 11:19 ` ical2org.py Eric S Fraga
2013-05-21 11:54 ` ical2org.py François Pinard
2013-05-21 13:10 ` ical2org.py Guido Van Hoecke
2013-05-21 15:09 ` ical2org.py aitor
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51953674.5030402@gmx.de \
--to=simon.thum@gmx.de \
--cc=aitors2005@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).