From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Christopher Witte <chris@witte.net.au>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>,
Greg Troxel <gdt@ir.bbn.com>
Subject: Re: Status google calendar sync
Date: Tue, 01 Feb 2011 09:07:24 +0000 [thread overview]
Message-ID: <87d3nc9l83.fsf@ucl.ac.uk> (raw)
In-Reply-To: <AANLkTik2WwfGhZh_-RqDHDymTNbd+Evc+0ROdy0vK_L-@mail.gmail.com> (Christopher Witte's message of "Mon, 31 Jan 2011 11:02:28 +0100")
Christopher Witte <chris@witte.net.au> writes:
> On 30 January 2011 02:21, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
>> Torsten Wagner <torsten.wagner@gmail.com> writes:
>>
>>
>> We need Emacs running on Android[1]. If Nokia can have Emacs native on
>> their phones (n900), why can't Android???
>>
>> I can dream.
>>
>> vi is available, but not vim (so far as I know) so can't do org that
>> way.
>>
>
> Apparently there is a native port of vim for android,
> http://credentiality2.blogspot.com/2010/08/native-vim-for-android.html
Thanks for this. I'll check it out. This could be the best route to
getting org mode native on Android! *And*, vi is more suitable for the
small keyboards (if any) on these devices...
--
Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)
next prev parent reply other threads:[~2011-02-01 9:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 14:53 Status google calendar sync Torsten Wagner
2011-01-29 19:38 ` Mark Elston
2011-01-29 20:44 ` Greg Troxel
2011-01-30 4:36 ` Mark Elston
2011-01-30 13:28 ` Greg Troxel
2011-01-30 14:09 ` Eric S Fraga
2011-01-30 20:43 ` Arun Persaud
2011-01-30 21:36 ` Mark Elston
2011-01-30 14:01 ` Eric S Fraga
2011-01-30 1:21 ` Eric S Fraga
2011-01-31 10:02 ` Christopher Witte
2011-02-01 9:07 ` Eric S Fraga [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-01 0:54 Torsten Wagner
2011-02-01 9:12 ` Eric S Fraga
2011-02-01 22:44 ` Sven Bretfeld
2011-02-02 5:15 ` Torsten Wagner
2011-02-02 8:30 ` Konrad Hinsen
2011-02-14 21:39 ` Marcelo de Moraes Serpa
2011-02-15 7:18 ` Konrad Hinsen
2011-02-15 16:37 ` Marcelo de Moraes Serpa
2011-02-15 16:43 ` Marcelo de Moraes Serpa
2011-02-15 16:55 ` Bastien
2011-06-10 16:58 ` Stephen Eglen
2011-06-10 17:04 ` Arun Persaud
2011-06-10 18:34 ` Stephen Eglen
2011-06-10 19:09 ` Arun Persaud
2011-06-11 13:25 ` Philipp Haselwarter
2011-06-11 18:38 ` Nick Dokos
2011-06-15 19:00 ` Eric S Fraga
2011-06-11 17:32 ` Niels Giesen
2011-06-30 16:14 ` Bastien
2011-06-15 18:45 ` Eric S Fraga
[not found] ` <87hb7rory9.fsf@ucl.ac.uk>
2011-06-16 12:13 ` Stephen Eglen
2011-01-21 8:38 Torsten Wagner
2011-01-21 9:43 ` Ian Barton
2011-01-21 15:22 ` Nick Dokos
2011-01-21 18:19 ` Arun Persaud
2011-01-21 23:58 ` Eric S Fraga
2011-01-25 20:21 ` Arun Persaud
2011-01-26 12:33 ` Eric S Fraga
2011-01-26 23:29 ` Mark Elston
2011-01-27 0:52 ` Arun Persaud
2011-01-27 2:51 ` Mark Elston
2011-01-27 19:43 ` Arun Persaud
2011-01-27 21:57 ` Arun Persaud
2011-01-28 16:13 ` Eric S Fraga
2011-01-31 19:03 ` Bastien
2011-01-29 1:28 ` Greg Troxel
2011-01-29 12:45 ` Eric S Fraga
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=87d3nc9l83.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=chris@witte.net.au \
--cc=emacs-orgmode@gnu.org \
--cc=gdt@ir.bbn.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).