From: "Jorge A. Alfaro Murillo" <firstname.lastname@example.org>
To: David Rogers <email@example.com>
Subject: Re: Agenda in MobileOrg for Android
Date: Tue, 9 Apr 2013 14:09:20 -0400 [thread overview]
Message-ID: <CAMxXW6-1r7ssYcxDSZgskxNs2KbLnH+eNPOk==MVU6Yjifmujg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2433 bytes --]
I think entries of the form
%%(org-class 2013 1 7 2013 4 27 2) 12:00pm-01:15pm TITLE
show up on MobileOrg.
I have org-mobile-agendas set up to 'default and they do for me.
Also the synchronization with Google Calendar is quite good in Android, you
can let then Google Calendar handles the remainders in your phone.
> Marcin Borkowski <firstname.lastname@example.org> writes:
>> Dnia 2013-04-07, o godz. 14:16:54
>> David Rogers <email@example.com> napisał(a):
>>> I have felt the same way. Is the reason it's not already done (and the
>>> pitfall for you if you take on a project like this) that "re-write
>>> major chunks of Emacs" is a pretty big job?
>> Remember that the purpose of something like such an app (as opposed to
>> Org-mode proper) would not be *editing* of text, but (primarily)
>> *entering* texts (and short ones, for that matter), entering
>> timestamps (which is quite convenient with any pointing device,
>> including touchscreens) and things like changing todo states and
>> clocking in and out - and that's basically it. In other words, a very
>> small subset of Org-mode is needed here (at least for me).
> I see what you mean. That makes more sense than what I said, and I like
> your idea.
> The part that I want most from Org-mode on Android is being able to
> automatically get audible reminders for all my appointments, whether
> through a transfer into the phone's own calendar or some other way. The
> current MobileOrg doesn't quite do the job, since it doesn't yet parse
> things like this:
> <%%(org-class 2013 03 01 2013 06 22 5 52 1 12 13)>
> ... In fact, last time I checked, it didn't even parse date stamps that
> weren't in the headline...
> ... so my whole Org file has to be specially formatted, and some of
> Org-mode's extremely useful features avoided, if I am going to satisfy
> MobileOrg's requirements.
> Being able to edit is nice, but that doesn't take advantage of what I
> really have the phone with me for - I see my phone as mainly a reminder
> machine, not mainly an editing machine, and would love to see MobileOrg
> (or some new project) gain the ability to parse every possible agenda
> feature used in Org files, so that I can actually receive reminders for
> all the items in my Org-mode agenda. If it came with a better way of
> simple editing, that would be even better.
[-- Attachment #2: Type: text/html, Size: 3005 bytes --]
next reply other threads:[~2013-04-09 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 18:09 Jorge A. Alfaro Murillo [this message]
2013-04-09 18:18 ` David Rogers
-- strict thread matches above, loose matches on Subject: below --
2013-04-07 17:54 Itai kloog
2013-03-24 1:52 Marcin Borkowski
2013-03-24 2:04 ` John Hendy
2013-04-07 13:13 ` Marcin Borkowski
2013-04-07 21:16 ` David Rogers
2013-04-07 21:41 ` Marcin Borkowski
2013-04-08 4:33 ` David Rogers
2013-04-08 6:24 ` Marcin Borkowski
2013-04-08 1:20 ` James Harkins
2013-04-08 9:26 ` Marcin Borkowski
2013-04-09 10:19 ` Gareth Smith
2013-04-08 6:52 ` James Harkins
2013-04-08 9:28 ` Marcin Borkowski
2013-04-09 18:24 ` Matthew Jones
2013-04-09 20:27 ` Marcin Borkowski
2013-04-09 20:51 ` Matthew Jones
2013-04-09 21:36 ` Marcin Borkowski
2013-04-09 22:06 ` John Hendy
2013-04-15 12:45 ` Andreas Leha
2013-04-15 15:24 ` Bastien
2013-04-15 18:36 ` Andreas Leha
2013-05-12 1:55 ` mobileorg-android
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).