emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Benoît Coste" <ben.coste@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: MobileOrg: adding new file
Date: Tue, 14 Jun 2016 12:20:05 +0000	[thread overview]
Message-ID: <CANJrASy=NZtoAw-GPn6U_sMZnAQq_+=AE7chTg16CvUfXCJyKw@mail.gmail.com> (raw)
In-Reply-To: <874m8yee12.fsf@saiph.selenimh>

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

Hello

So what I wanted to discuss was the possibility for a MobileOrg to create
new files from its phone and keep them synched.

Currently the list of synched files is a file called "index.org" stored in
the synch folder and Emacs and MobileOrg use ite for pulling changes.
However everytime Emacs pushes a changes, it overwrites this file. Because
for pushing, Emacs use a second list of files, the variable
'org-agenda-files and it will recreate a new index.org based on
org-agenda-files content. To conclude, if MobileOrg had added a file to
synch in index.org, it will be removed from the list after next Emacs push.

So my suggestion is for Emacs to stop using org-agenda-files to generate
the list of synched file but use the currently existing index.org. In case
index.org does not exist (for eg. at repo initialization), then
org-agenda-files can be used to create it.

To be honest, after a lot of reflexion, I think more and more about using a
external synch mechanism (such as git) instead of using org-mobile.el. A
positive point would be to allow non-Emacs people to use MobileOrg with
synchronization. So I may not even use my own suggestion but I still think
it is worth to mention this "incoherence".

Regards

On Sun, Jun 12, 2016 at 3:24 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Benoît Coste <ben.coste@gmail.com> writes:
>
> > I am working on remodeling MobileOrg for Android and I'd like to discuss
> a
> > few changes for mobile-org.el.
>
> I read your mail from a month ago. Unfortunately, I don't know enough of
> this library to be useful to the discussion.
>
> > I am trying to contact the maintainer of mobile org. The file
> mobile-org.el
> > says carsten@orgmode.org but I tried it and it is not working. Does
> anyone
> > know who is currently maintaining mobile-org.el ?
>
> It is part of Org core, so anyone with write access to repository can
> maintain it. The current maintainer is Bastien Guerry, who reads this
> list. IOW, you can discuss the changes here.
>
> Regards,
>
> --
> Nicolas Goaziou
>

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

  reply	other threads:[~2016-06-14 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-12 12:33 mobile-org.el maintainer Benoît Coste
2016-06-12 13:24 ` Nicolas Goaziou
2016-06-14 12:20   ` Benoît Coste [this message]
2016-06-15  8:46     ` MobileOrg: adding new file Philip Hudson

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='CANJrASy=NZtoAw-GPn6U_sMZnAQq_+=AE7chTg16CvUfXCJyKw@mail.gmail.com' \
    --to=ben.coste@gmail.com \
    --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).