From mboxrd@z Thu Jan 1 00:00:00 1970 From: Henning Weiss Subject: Re: Android MobileOrg: appointments without SCHEDULED/DEADLINE Date: Wed, 24 Apr 2013 19:21:05 +0200 Message-ID: References: <20130324025258.521fa38a@aga-netbook> <20130407151332.218212de@aga-netbook> <20130408112847.769a44d3@aga-netbook> <2013-04-23T12-38-46@devnull.Karl-Voit.at> <877gjsczg6.dlv@debian.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2bcf0e28ae004db1e86c6 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34536) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UV3Nl-0000qD-Qz for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 13:21:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UV3Ng-0002zX-Ku for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 13:21:25 -0400 Received: from mail-qc0-x235.google.com ([2607:f8b0:400d:c01::235]:59317) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UV3Ng-0002zP-FI for emacs-orgmode@gnu.org; Wed, 24 Apr 2013 13:21:20 -0400 Received: by mail-qc0-f181.google.com with SMTP id a22so1069244qcs.26 for ; Wed, 24 Apr 2013 10:21:20 -0700 (PDT) In-Reply-To: <877gjsczg6.dlv@debian.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --001a11c2bcf0e28ae004db1e86c6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, On Wed, Apr 24, 2013 at 6:41 AM, R=E9mi Vanicat wrote: > Karl Voit writes: > > > Hi! > > > > * Matthew Jones 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. > You are correct, repeating timestamps do not work yet. You can find the associated issue here. This is one of the next major things we'll be working on. Henning --001a11c2bcf0e28ae004db1e86c6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

On We= d, Apr 24, 2013 at 6:41 AM, R=E9mi Vanicat <vanicat@debian.org> wrote:
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 =A0 = :rem15:

I use :

** this is an event/appointment =A0 :rem15:
=A0 <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

=A0 <2013-05-07 Tue 9:00-11:00 +1w>

in a recurring event, and I would really like this to be solved.

You are correct, repeating timestamps do not work yet. You can f= ind the associated issue=A0here. This is one of the next major things we'll be workin= g on.

Henning=A0
--001a11c2bcf0e28ae004db1e86c6--