emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Loury <konubinix@gmail.com>
To: Matt Lundin <mdl@imapmail.org>, Xebar Saram <zeltakc@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: syncing my life (orgmode :)) to a mobile (android)	device..cant find a holistic reliable way..how do you guys	manage to do it?
Date: Mon, 07 Dec 2015 11:30:31 +0100	[thread overview]
Message-ID: <878u56v9dk.fsf@gmail.com> (raw)
In-Reply-To: <87a8poiuxw.fsf@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 1486 bytes --]

Matt Lundin <mdl@imapmail.org> writes:

> Xebar Saram <zeltakc@gmail.com> writes:
>>
>> So my question is (sorry for the long intro :)) what do orgmode users
>> (who also are heavy mobile users) do? do they give up on contacts and
>> calendaring on the mobile? maintain 2 separate databases? what tools
>> do people use to overcome this issue?
>
> There are lots of way to sync calendars. See
> http://orgmode.org/worg/org-tutorials/org-google-sync.html
>
> I've found the easiest method is a "poor man's sync" involving a
> read-only ics file (exported from org using the org-icalendar-*
> functions) and a writable calendar for new entries. (Trying to map org
> entries to ics entries gets messy.) The flow looks something like this:
>
> writable calendar (remote calendar for adding new items from android)
> ----> org files (with new entries pull from remote calendar) ---->
> read-only calendar (remote ics exported from org)
>
> I use a radicale server[fn:1] for this. Radicale has the advantage of
> using ics files as a backend (rather than a database), so I can pull new
> entries into org with Eric's ical2org.awk.

I do exactly the same thing, also with radicale running in a chrooted
debian in my android phone. I am not happy with this solution since it
is not bidirectional but I agree it is the easiest method as far as I am
concerned.

-- 
Konubinix
GPG Key    : 7439106A
Fingerprint: 5993 BE7A DA65 E2D9 06CE  5C36 75D2 3CED 7439 106A

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2015-12-07 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-05  7:10 syncing my life (orgmode :)) to a mobile (android) device..cant find a holistic reliable way..how do you guys manage to do it? Xebar Saram
2015-12-05 14:08 ` Eric S Fraga
2015-12-05 15:12   ` Xebar Saram
2015-12-05 17:43   ` Bingo UV
2015-12-07 12:09     ` Eric S Fraga
2015-12-07 12:48   ` Detlef Steuer
2015-12-05 18:58 ` Matt Lundin
2015-12-07 10:30   ` Samuel Loury [this message]
2016-01-27 14:02   ` syncing my life (orgmode :)) to a mobile (android) device Karl Voit
2015-12-06 18:27 ` syncing my life (orgmode :)) to a mobile (android) device..cant find a holistic reliable way..how do you guys manage to do it? Jorge A. Alfaro-Murillo
2015-12-07  4:00 ` Bob Newell
2015-12-07  9:15 ` Ramon Diaz-Uriarte

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=878u56v9dk.fsf@gmail.com \
    --to=konubinix@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=zeltakc@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.
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).