From: "Rémi Vanicat" <vanicat@debian.org>
To: emacs-orgmode@gnu.org
Subject: Re: Android MobileOrg: appointments without SCHEDULED/DEADLINE
Date: Wed, 24 Apr 2013 06:41:45 +0200 [thread overview]
Message-ID: <877gjsczg6.dlv@debian.org> (raw)
In-Reply-To: 2013-04-23T12-38-46@devnull.Karl-Voit.at
Karl Voit <devnull@Karl-Voit.at> writes:
> Hi!
>
> * Matthew Jones <bsdmatburt@gmail.com> wrote:
>> - If you have issues and you don't tell us then we have no way of helping
>> you and the problem might not go away.
>
> I mainly use MobileOrg on my Android phone to capture URLs and
> tasks and I am *very* thankfully for this possibility!
>
>
> However, with Google getting untrustworthy (Reader, APIs, ...), I
> want to get rid of Google Calendar as well. As you can read in [1],
> many people are creating appointments by simply adding an active
> time-stamp without SCHEDULED/DEADLINE or TODO states:
>
> ** <2013-05-07 Tue 9:00-11:00> this is an event/appointment :rem15:
I use :
** this is an event/appointment :rem15:
<2013-05-07 Tue 9:00-11:00>
And my android sync it with the agenda.
I Just confirmed by testing that the bug is with timestamp on the
headline line.
My main problem with mobilorg is that it do not translate
<2013-05-07 Tue 9:00-11:00 +1w>
in a recurring event, and I would really like this to be solved.
[...]
--
Rémi Vanicat
next prev parent reply other threads:[~2013-04-24 4:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 1:52 Agenda in MobileOrg for Android 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-23 10:50 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE (was: Agenda in MobileOrg for Android) Karl Voit
2013-04-24 4:41 ` Rémi Vanicat [this message]
2013-04-24 7:38 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE Eric S Fraga
2013-04-24 14:46 ` Rémi Vanicat
2013-04-24 17:21 ` Henning Weiss
2013-04-24 17:33 ` MobileOrg and repeating events (was: Android MobileOrg: appointments without SCHEDULED/DEADLINE) Karl Voit
2013-04-24 17:15 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE (was: Agenda in MobileOrg for Android) Henning Weiss
2013-04-24 17:30 ` Karl Voit
2013-04-25 8:55 ` Android MobileOrg: appointments without SCHEDULED/DEADLINE Eric S Fraga
2013-04-15 12:45 ` Agenda in MobileOrg for Android Andreas Leha
2013-04-15 15:24 ` Bastien
2013-04-15 18:36 ` Andreas Leha
2013-05-12 1:55 ` mobileorg-android
2013-05-13 3:00 ` [mobileorg-android] " James Harkins
2013-05-13 13:28 ` Marcin Borkowski
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=877gjsczg6.dlv@debian.org \
--to=vanicat@debian.org \
--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).