From: Matthew Jones <bsdmatburt@gmail.com>
To: Renato <rennabh@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: android mobile org question on capture
Date: Sat, 18 Feb 2012 13:28:17 -0500 [thread overview]
Message-ID: <CABSYn2i4P5GMOS9kxAggBtiYHAV7z4TygwF4DfKavXS4pXOtew@mail.gmail.com> (raw)
In-Reply-To: <20120217152409.52cef9bc@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
Hi Renato, I'm the maintainer of MobileOrg for Android.
Regarding #1 this seems like an org-mode thing and I'm not too sure...
usually I just look at these and file them manually, but this could get
untenable if you have a lot of content
on #2 I think we have it solved here:
https://github.com/matburt/mobileorg-android/issues/168
and it will be available in the next version (0.8.4+)
Thanks :)
On Fri, Feb 17, 2012 at 9:24 AM, Renato <rennabh@gmail.com> wrote:
> Hi, I have finally set up mobile org on my android phone, with calendar
> sync, and like it very much.
>
> Regarding the capture functionality, is it (or will it be) possible to:
>
> 1) define wich file and under which header the TODOs get written to. I
> have a notes.org file with Todo section where I store all my generic
> TODOs... alternativly I guess I could set up an automated refile when
> calling org-mobile-pull
>
> 2) define SCHEDULED and DEADLINE for the note. This would also be handy
> because captured notes would appear right away in my android
> calendar, without having to get to my pc, org-mobile-pull, add a
> deadline, refile, and finally org-mobile-push.
>
> I just upgraded from 0.8.0 to 0.8.3
>
> cheers and a big thank you to who is writing this software,
> renato
>
>
[-- Attachment #2: Type: text/html, Size: 1777 bytes --]
next prev parent reply other threads:[~2012-02-18 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 14:24 android mobile org question on capture Renato
2012-02-18 18:28 ` Matthew Jones [this message]
2012-02-18 18:32 ` Renato
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABSYn2i4P5GMOS9kxAggBtiYHAV7z4TygwF4DfKavXS4pXOtew@mail.gmail.com \
--to=bsdmatburt@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rennabh@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.