From: Peter Davis <pfd@pfdstudio.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: MobileOrg
Date: Sat, 21 Nov 2015 18:24:32 -0500 [thread overview]
Message-ID: <m2vb8vj5qm.fsf@PFDStudio-Air.home> (raw)
In-Reply-To: <CA+M2ft83u0svDtOTT4F3y2rg7Nv6eDYto1YEvyTzgY6+MNEk9Q@mail.gmail.com> (John Hendy's message of "Sat, 21 Nov 2015 12:44:34 -0600")
John Hendy <jw.hendy@gmail.com> writes:
> On Sat, Nov 21, 2015 at 9:42 AM, Peter Davis <pfd@pfdstudio.com> wrote:
>>
>> On Fri, Nov 20, 2015, at 03:58 PM, dean wrote:
>>> On 11/21/15 00:14, Peter Davis wrote:
>>> Hi pd,
>>>
>>> > I'm just starting out with MobileOrg, using Dropbox, but I'm confused by the setup instructions. I've gotten the app linked to my
>>> > Dropbox account, but the next step in the setup instructions <http://mobileorg.ncogni.to/doc/getting-started/using-dropbox/> involve
>>> > setting up some emacs stuff on my "local system." My question is: *Which* local system? I have several sync'ed to Dropbox. Is the
>>> > mobile app going to require a single point of contact?
>
> Well, to my knowledge, mobile-org isn't meant to function as a way to
> sync a bunch of emacs/org setups, ...
Yes, that is the function of Dropbox. In my setup, I have org files in
several directories within the ~/Dropbox/... tree. What I failed to
understand earlier is that MobileOrg syncs with one and only one
directory, so when I'm on a desk/laptop machine, I have to either edit
directly in ~/Dropbox/Apps/MobileOrg/, or use org-mobile-push to copy
all my files, in their current state, to that directory. That was the
piece I missed.
> ... so yes. You'd have one primary
> system with your files to sync, you'd push to Dropbox from that
> system, and the changes would get picked up from the phone.
All of my .org files are already in the ~/Dropbox tree, but in various
directories.
> Changes/additions from the phone are not automatic, to my knowledge.
> These get put in the file pointed to by =org-mobile-inbox-for-pull=,
> which you can then re-file or whatever into your main org files. You
> could certainly sync various files with Dropbox on several systems,
> re-create the same local mobileorg setup on said systems, edit them
> from the Dropbox folder and invoke org-mobile-push from that system.
> This will use Dropbox to sync the local file since it's under Dropbox
> control, and also update it for your phone.
>
>>> >
>>>
>>> Im fairly new to emacs and mobileorg, so im no expert here but...
>>> I believe Mobile org will be using your dropbox folder as its single
>>> point of contact.
>>> For example your workflow would be:
>>> - Create/edit notes/todo's on your phone
>>> - sync the app (which should save to dropbox)
>>> - Open emacs on your pc, issue org-mobile-pull
>>> - This should add your edits to your org files on your pc
>>>
>>> For the other direction:
>>> - Edit org files on your pc, issue org-mobile-push
>>> - sync on the app should import your edits into the app
>>>
>>> Im assuming you have a dropbox daemon taking care of the syncing in this
>>> process.
>>>
>>> This should be the same no matter how many pc's/emacs you use.
>>> Does this help answer your question?
>>>
>>
>> Thanks, Dean. Actually, I can't even sync mobileorg. When I try
>> (Pressing the sync button in the upper right corner), I get:
>>
>
> Well, like my comments on your subtree export thread, no one can
> diagnose what they can't reproduce. You've literally supplied no
> information about what you've done.
The errors I encountered were all in MobileOrg, so there was no
information to supply other than the message that MobileOrg displayed,
which I did include.
> Did you set any of the variables
> described in the manual? What are they set to?
As I understood it, the exchange between MobileOrg and Dropbox is
independent of any one particular machine and it's emacs setup, so the
variables seemed irrelevant.
> Did you run =M-x
> org-moble-push=?
No, I overlooked that step.
>Do you have the Dropbox daemon on so that the changes
> were pushed to the cloud?
Yes.
> You're doing yourself a serious disservice
> by not posting full details and reproducible examples. 1) you're going
> to get *vastly* less responses because people don't even know what to
> make of the post and won't try, and 2) people will get frustrated
> making a suggestion to one email (say, about directing you on how to
> use mobileorg) and meeting a response that's completely different (I
> can't get it to sync due to checksums.dat missing).
How is this response different? This *is* the problem I encountered in
trying to use MobileOrg.
> Basically, these
> detail lacking posts waste the time of others.
I do try to supply as much detail as I can, and I appreciate your and
others' efforts to help me unravel these problems. Thank you.
> I've been wanting to try mobileorg for some time so I took the time to
> go through the instructions from scratch. See attached pdf and .org
> file. I can't verify that mobileorg picks it up on my phone because
> Dropbox is down, but the created file structure in ~/Dropbox/MobileOrg
> looks sane. I'll try dropbox later to see if that part succeeds.
>
>
> John
>
>>
>> *Error downloading checksums*
>>
>> An error was encountered while downloading checksums.dat from the
>> server. The file isn't required, but the error received was unusual. The
>> error was:
>>
>> Unexpected error
>>
>>
>> I don't know what that's about, but I can't get past it.
>>
Thanks!
-pd
next prev parent reply other threads:[~2015-11-21 23:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:14 MobileOrg Peter Davis
2015-11-20 20:58 ` MobileOrg dean
2015-11-21 15:42 ` MobileOrg Peter Davis
2015-11-21 18:44 ` MobileOrg John Hendy
2015-11-21 23:24 ` Peter Davis [this message]
2015-11-21 23:39 ` MobileOrg John Hendy
2015-11-21 19:07 ` MobileOrg Ed Hirgelt
2015-11-21 21:17 ` MobileOrg John Hendy
2015-11-21 22:05 ` MobileOrg dean
2015-11-21 22:52 ` MobileOrg Peter Davis
2015-11-21 23:25 ` MobileOrg John Hendy
2015-11-21 23:30 ` MobileOrg dean
2015-11-21 23:52 ` MobileOrg Peter Davis
2015-11-22 6:34 ` MobileOrg dean
2015-11-22 13:43 ` MobileOrg Peter Davis
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 14:07 MobileOrg Noah Slater
2014-08-06 16:11 ` MobileOrg Subhan Michael Tindall
2014-08-06 16:33 ` MobileOrg Alexis
2014-08-06 18:33 ` MobileOrg Xebar Saram
2014-08-14 1:50 ` MobileOrg Sean Escriva
2014-02-28 4:34 MobileOrg David Masterson
2014-03-01 7:07 ` MobileOrg Bastien
2014-03-02 3:14 ` MobileOrg John Hendy
2014-03-02 3:20 ` MobileOrg John Hendy
2014-03-03 19:20 ` MobileOrg Sean Escriva
2014-03-03 19:29 ` MobileOrg Ken Mankoff
2014-03-15 0:12 ` MobileOrg Aric Gregson
2014-03-15 0:50 ` MobileOrg Sean Escriva
2014-03-15 0:59 ` MobileOrg Aric Gregson
2014-06-25 18:56 ` MobileOrg Aric Gregson
2014-06-25 19:17 ` MobileOrg Nick Dokos
2014-07-04 0:47 ` MobileOrg Aric Gregson
2014-07-04 13:14 ` MobileOrg Nick Dokos
2014-07-04 13:17 ` MobileOrg Nick Dokos
2013-03-13 13:09 mobileorg Marvin Doyley
2013-03-13 13:53 ` mobileorg Rainer M Krug
2013-03-14 11:13 ` mobileorg Rasmus
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=m2vb8vj5qm.fsf@PFDStudio-Air.home \
--to=pfd@pfdstudio.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@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).