From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: MobileOrg documentation?
Date: Fri, 08 Aug 2014 10:38:50 -0400 [thread overview]
Message-ID: <87vbq3cah1.fsf@yale.edu> (raw)
In-Reply-To: 86egwrjznk.fsf@gmail.com
David Masterson <dsmasterson@gmail.com> writes:
> Not looking for complete org functionality in my phone -- just a
> reasonable ability to edit org outlines while I'm on the road.
Well you can do that with MobileOrg... sort of. Once you edit and
save a change, synchronize in your phone and then pull from your
computer (org-mobile-pull). From (info (org) Pulling from
MobileOrg):
"Some changes are applied directly and without user interaction.
Examples are all changes to tags, TODO state, headline and body
text that can be cleanly applied. Entries that have been flagged
for further action will receive a tag ‘:FLAGGED:’, so that they
can be easily found again. When there is a problem finding an
entry or applying the change, the pointer entry will remain in the
inbox and will be marked with an error message. You need to later
resolve these issues by hand."
I do not understand when "cleanly applied" is the case, but my
experience is that resolving "these issues by hand" is the most
likely outcome. Even simple edits in the text of an entry in my
phone generally result in errors of synchronization. Note that
besides adding a comment of when the file was changed in the
mobile, the local file does not change. Also you can see the
differences in the files in the from-org-mobile.org file (or
whatever you set the org-mobile-inbox-for-pull variable to).
Because of this limitation, I am better off just adding simple
captures on my phone as remainders to do something in my computer,
even adding information to a certain file. Then, when I
synchronize in the phone and pull in my computer, the only file
that changes is from-org-mobile.org, I open that buffer and use
org-refile to send things to the right place. Save all org
buffers, org-mobile-push and repeat.
I you have access by ssh to a computer that is always on, then I
recommend leaving an emacsclient open and using JuiceSSH of
ConnectBot for editing your org files on the go.
Best,
--
Jorge.
next prev parent reply other threads:[~2014-08-08 14:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 4:26 MobileOrg documentation? David Masterson
2014-08-07 0:36 ` John Hendy
2014-08-07 7:13 ` David Masterson
2014-08-07 7:28 ` Alexis
2014-08-07 13:41 ` Jorge A. Alfaro-Murillo
2014-08-07 13:52 ` Jorge A. Alfaro-Murillo
2014-08-07 14:11 ` Ramon Diaz-Uriarte
2014-08-08 5:53 ` David Masterson
2014-08-08 6:08 ` Xebar Saram
2014-08-08 14:38 ` Jorge A. Alfaro-Murillo [this message]
2014-08-08 17:42 ` David Masterson
2014-08-08 18:28 ` Jorge A. Alfaro-Murillo
2014-08-08 18:58 ` Ken Mankoff
2014-08-08 19:40 ` Jorge A. Alfaro-Murillo
2014-08-08 21:18 ` David Masterson
2014-08-08 22:17 ` Nick Dokos
2014-08-08 21:15 ` David Masterson
2014-08-08 21:19 ` Ken Mankoff
2014-08-13 12:26 ` Jason F. McBrayer
2014-08-13 18:28 ` Xebar Saram
2014-08-18 13:48 ` root
2014-08-18 8:16 ` Eric S Fraga
2014-08-07 13:58 ` Eric Abrahamsen
2014-08-07 14:39 ` hymie!
2014-08-07 15:57 ` Subhan Michael Tindall
2014-08-07 20:09 ` Christian Kruse
2014-08-07 21:53 ` Jacob Gerlach
2014-08-14 1:57 ` Sean Escriva
2014-08-16 17:49 ` Usage, OPML, Toodledo (was Re: MobileOrg documentation?) David Masterson
2014-08-14 2:02 ` MobileOrg documentation? Sean Escriva
2014-08-14 4:56 ` Carlos Sosa
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=87vbq3cah1.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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).