emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-caldav will cease to work with Google Calendar
Date: Sat, 16 Mar 2013 13:32:04 +0100	[thread overview]
Message-ID: <87obejeda3.fsf@pank.iue.private> (raw)
In-Reply-To: 87wqt8wsjc.fsf@engster.org

David Engster <deng@randomsample.de> writes:

> 'rasmus' writes:
>> For now I'm using fluux, but I haven't managed to get org-CalDAV to
>> sync yet.
>
> What is that? I'm afraid I cannot find it.


Sorry, that's a typo.

     http://fruux.com.

It works with the aCal package which is in the F-Droid archive for
Android software.

>>  I'm also looking to sync bbdb via CardDAV, although I would be
>> willing to switch to org-contacts if a solution emerged here before.
>
> CardDAV shouldn't be very hard to add. There are two reasons however why
> at least I won't work on this in the near future: I don't need it, and
> it's boring.

Fair enough.  A natural place to add it is the ASynK package. . .

>> Baïkal and Radicale are nice, small CalDAV servers.  The latter also
>> provides CardDAV.
>
> I just discovered Radicale. I think it is very nice for people who don't
> want/need a full-blown Workgroup or Cloud solution like SOGo/Owncloud.
> org-caldav does not currently work with it, but this should be fixable.

What I would need would be something I can install as an unprivileged
user on a remote host.  For instance something that could be called
over SSH. . .  I could install/compile Radicale on my remote host, but
I don't know whether I would be able to access it when it's not
running as a 'root' service. . .

–Rasmus

-- 
Vote for proprietary math!

  reply	other threads:[~2013-03-16 12:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 16:19 org-caldav will cease to work with Google Calendar David Engster
2013-03-14 17:03 ` Bastien
2013-03-14 17:13   ` David Engster
2013-03-14 17:06 ` Torsten Wagner
2013-03-14 22:48 ` Julien Cubizolles
2013-03-14 23:01   ` Charles Philip Chan
2013-03-15  8:23     ` Julien Cubizolles
2013-03-15  9:05       ` Sebastien Vauban
2013-03-15 10:29         ` Julien Cubizolles
2013-03-15  9:25       ` Charles Philip Chan
2013-03-15 10:43         ` Julien Cubizolles
2013-03-15 14:16     ` Eric S Fraga
2013-03-15 14:25       ` Torsten Wagner
2013-03-17 12:57         ` Eric S Fraga
2013-03-15 14:14 ` Eric S Fraga
2013-03-15 15:06 ` Rasmus
2013-03-15 15:25   ` Marcin Borkowski
2013-03-15 16:12   ` David Engster
2013-03-16 12:32     ` Rasmus [this message]
2013-03-15 17:48 ` Vincent Beffara
2013-03-15 18:05   ` David Engster
2013-03-16 17:30     ` Vincent Beffara
2013-03-19 16:43       ` Vincent Beffara
2013-06-06 18:44 ` org-caldav will continue to work with Google Calendar (was: org-caldav will cease to work with Google Calendar) David Engster
2013-06-07 18:57   ` org-caldav will continue to work with Google Calendar Eric S Fraga
2013-06-18  9:09   ` Eric S Fraga
2013-06-18 10:09     ` 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

  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=87obejeda3.fsf@pank.iue.private \
    --to=rasmus@gmx.us \
    --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).