From: Eric S Fraga <esflists@gmail.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: *Good* client for Android?
Date: Fri, 13 Oct 2017 07:28:10 +0100 [thread overview]
Message-ID: <87sheny32d.fsf@gmail.com> (raw)
In-Reply-To: <4916869e-5f2d-479c-b4a6-864d771be3c9@complete.org> (John Goerzen's message of "Thu, 12 Oct 2017 16:28:42 -0500")
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
On Thursday, 12 Oct 2017 at 16:28, John Goerzen wrote:
> Hi folks,
>
> All along, I anticipated using this with Android (and, ideally, also
> iOS). The MobileOrg feature set looked great, and the syncing mechanism
> looked a lot better than sharing Dropbox.
>
> I use git to share my ~/org between two computers (laptop and desktop),
> using git-remote-gcrypt to store on a server. This makes syncing and
> resolving conflicts easy (I move between the two throughout the day, so
> Dropbox is really not a great option here.) Sync integrity -- or at
> least robust detection of conflicts -- is a must. Encryption is a "very
> nice to have."
>
> Suggestions?
I am not sure what you are asking for. What is missing in MobileOrg?
You say it is suffering from bitrot but it works just fine for me on a
daily basis, with no issues having multiple Android devices using the
same location. Okay, it no longer works with Dropbox but it does work
with a number of other media.
Maybe I missed it but what is not clear is what features you actually
require that you don't have other than the encryption aspect mentioned
above.
For instance, I have recently started playing with org-dropbox [1] for
capturing notes from an Android device. But I will keep using MobileOrg
as I need Google calendar synchronisation.
The only way to truly work with org on your phone would be to have Emacs
on your phone. That *is* possible but the currently available solutions
are less than useful (IMO). The second best is to ssh to a system
running Emacs (as has already been suggested).
My own full solution is to have a palm sized computer running Emacs: the
Pandora [2] which is (hopefully) soon to be replaced by the Pyra [3].
eric
Footnotes:
[1] https://github.com/heikkil/org-dropbox
[2] https://en.wikipedia.org/wiki/Pandora_(console)
[3] https://pyra-handheld.com/boards/pages/pyra/
--
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-10-13 6:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:28 *Good* client for Android? John Goerzen
2017-10-12 23:01 ` Martin Alsinet
2017-10-12 23:02 ` John Goerzen
2017-10-13 6:28 ` Eric S Fraga [this message]
2017-10-13 13:34 ` John Goerzen
2017-10-13 13:49 ` Eric S Fraga
2017-10-13 16:45 ` Leslie Watter
2017-10-13 8:47 ` Neil Jerram
2017-10-13 13:28 ` John Goerzen
2017-10-25 13:36 ` Adonay Felipe Nogueira
-- strict thread matches above, loose matches on Subject: below --
2017-10-14 4:30 Eric Thomas
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=87sheny32d.fsf@gmail.com \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jgoerzen@complete.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).