From: Bingo UV <right.ho@gmail.com>
To: emacs-orgmode@gnu.org
Subject: 20150810 broke Android mobileorg synchronization?
Date: Wed, 12 Aug 2015 21:50:48 +0530 [thread overview]
Message-ID: <20150812215048.56479371@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]
Hi,
Ever since I upgraded to 20150810 from orgmode elpa, mobileorg
synchronization with Android phone has stopped working[1]. Earlier
org version was from around 13 July. From my older mobileorg pushed
files, I see two important differences:
1. index.org with 20150810 contains extra header commented lines of TODO and
DRAWERS, which are incorrect.
Pre 20150810
--------------------------------------------------------------
#+READONLY
#+TODO: TODO WAITING NEXT INPROGRESS DONE
#+TAGS: =====IDENTICAL TAGS LINE====================
#+ALLPRIORITIES: A B C
--------------------------------------------------------------
In 20150810
--------------------------------------------------------------
#+READONLY
#+TODO: TODO WAITING NEXT INPROGRESS DONE
#+TODO: | DONE
#+TAGS: =====IDENTICAL TAGS LINE====================
#+DRAWERS: PROPERTIES CLOCK LOGBOOK RESULTS
#+ALLPRIORITIES: A B C
--------------------------------------------------------------
Once I remove these extra TODO and DRAWERS lines from mobileorg's index.org, mobileorg
synchronization with Android mobileorg application starts working again, but this needs
to be done for every push.
2. All agenda org files contain extra PROPERTIES drawer for every entry. While it is not
blocking synchronization, it increases file sizes significantly and might cause problems
in editing the file using simple scripts. Example of one entry is below, every entry at
every level seems to have this extra entry.
Pre 20150810
--------------------------------------------------------------
*** NEXT sampletodoitem
:LOGBOOK:
- State "NEXT" from "TODO" [2015-07-08 Wed 21:18]
- State "TODO" from "" [2015-07-08 Wed 21:18]
:END:
:PROPERTIES:
:ID: c035368f-cd7b-4159-bcc6-01632f4f8860
:END:
--------------------------------------------------------------
In 20150810
--------------------------------------------------------------
*** NEXT sampletodoitem
:PROPERTIES:
:ID: 9363d19f-84bc-4872-a77c-b931448e253c
:END:
:LOGBOOK:
- State "NEXT" from "TODO" [2015-07-08 Wed 21:18]
- State "TODO" from "" [2015-07-08 Wed 21:18]
:END:
:PROPERTIES:
:ID: c035368f-cd7b-4159-bcc6-01632f4f8860
:END:
--------------------------------------------------------------
Can someone else confirm or deny these findings?
[1]: By stopped working, I mean "Clear database", then Synchronize causes only one entry (Agenda Views) to appear in
mobileorg UI, that one entry is empty. Synchronize again causes one more entry (first org file) to appear, which is
also empty. And so on.
thanks
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-08-12 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150812215048.56479371@gmail.com \
--to=right.ho@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).