From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: MobileOrg documentation?
Date: Fri, 08 Aug 2014 18:17:22 -0400 [thread overview]
Message-ID: <87bnruiq31.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 86bnruwuhx.fsf@gmail.com
David Masterson <dsmasterson@gmail.com> writes:
> jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
>> Ken Mankoff writes:
>>
>>> On iPhone, you cannot add sub-headings.
>>
>> Another good reason to ditch your iPhone and buy a Nexus =)
>>
>> Even when the Android and iPhone applications are different, the good
>> thing is that the org side (org-mobile.el) is not specific for the
>> iPhone or Android (or any external application that uses the same
>> conventions).
>>
>> Perhaps that is why the manual seems to new users so vague, they
>> expect that it will explain how to go over the phone installation as
>> well. But that is not the job of the org part, but that of the phone
>> application IMO.
>
> But, the Org part should, at least, point to the documentation of the
> phone part. At the very least, provide a place for the phone part(s) to
> be documented on Worg and point there...
It does. There is an iOS pointer and an Android pointer in
(info "(org) Appendix B MobileOrg")
For iOS, it says:
,----
| The iOS implementation (https://github.com/MobileOrg/) for the
| iPhone/iPod Touch/iPad series of devices, was started by Richard
| Moreland and is now in the hands Sean Escriva.
`----
And if you follow that link, you'll get to another link
http://mobileorg.ncogni.to/
which has a "Documentation" button - I didn't push the button but I hope
there is something substantive behind it.
--
Nick
next prev parent reply other threads:[~2014-08-08 22:17 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
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 [this message]
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=87bnruiq31.fsf@alphaville.bos.redhat.com \
--to=ndokos@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).