emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Xebar Saram <zeltakc@gmail.com>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Some thoughts on MobileOrg and its development ....
Date: Thu, 14 Aug 2014 18:29:49 +0300	[thread overview]
Message-ID: <CAOQHXPqQJY+1LG8Kpuf+0RuUo3WvyT=+Lx9R=r69bp2=E7qQng@mail.gmail.com> (raw)
In-Reply-To: <87bnrni467.fsf@yale.edu>

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

would LOVE to try it as well

thx!

z


On Thu, Aug 14, 2014 at 4:36 PM, Jorge A. Alfaro-Murillo <
jorge.alfaro-murillo@yale.edu> wrote:

> Eric Abrahamsen writes:
>
>> Henning Weiss <hdweiss@gmail.com> writes:
>>
>>> I have been working over the last couple of months on a private
>>> prototype. I'm currently using it in my daily life and it works for me. It
>>> uses Git (and only Git) for synchronization and doesn't use org-mobile at
>>> all. The idea is that you keep all org files under git version control.
>>> Synchronization of all "clients" (apps or Emacs) is done against that
>>> repository. It is also possible to configure whether to use "ours" or
>>> "theirs" merge strategy when conflicts occur. I have focused on designing
>>> an app I can trust.
>>> It already has an outline view like MobileOrg, an agenda view, you can
>>> add and edit nodes, synchronize changes with a remote repository and
>>> synchronize scheduled entries to the calendar. I ported some of my code
>>> from MobileOrg, but a lot of it is written from scratch.
>>>
>>
> Sounds great... can't wait!
>
>
>
>> Maybe you could publish a very basic how-to here, and then we could annoy
>> you privately with problems?
>>
>
> That's a good idea, 1+
>
> --
> Jorge.
>
>
>

[-- Attachment #2: Type: text/html, Size: 2168 bytes --]

  reply	other threads:[~2014-08-14 15:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09  0:56 Some thoughts on MobileOrg and its development Alexis
2014-08-09  4:13 ` Xebar Saram
2014-08-09  4:22 ` David Masterson
2014-08-13  1:07   ` Ashton Kemerling
2014-08-13  1:47     ` David Wagle
2014-08-13  2:23       ` Ashton Kemerling
2014-08-13  2:45         ` Alexis
2014-08-13  4:04           ` Ashton Kemerling
2014-08-13  8:10           ` Jacek Generowicz
2014-08-13 22:23             ` Carlos Sosa
2014-08-14  0:54               ` Alexis
2014-08-13  2:59       ` Alexis
2014-08-09  7:53 ` Jacek Generowicz
2014-08-14  1:47   ` Sean Escriva
2014-08-14  2:10     ` Ashton Kemerling
2014-08-14 10:17     ` Jacek Generowicz
2014-08-14 12:17       ` Henning Weiss
2014-08-14 13:07         ` Eric Abrahamsen
2014-08-14 13:36           ` Jorge A. Alfaro-Murillo
2014-08-14 15:29             ` Xebar Saram [this message]
2014-08-18  7:20               ` Samuel Loury
2014-09-10 19:39                 ` Samuel Loury

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='CAOQHXPqQJY+1LG8Kpuf+0RuUo3WvyT=+Lx9R=r69bp2=E7qQng@mail.gmail.com' \
    --to=zeltakc@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jorge.alfaro-murillo@yale.edu \
    /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).