From: Stefan Huchler <stefan.huchler@mail.de>
To: emacs-orgmode@gnu.org
Subject: Re: backend for todo.txt format (todotxt.com)
Date: Sun, 17 Jan 2016 03:21:03 +0100 [thread overview]
Message-ID: <87wpr9uezv.fsf@jupiter.lan> (raw)
In-Reply-To: 87ziw59tmx.fsf@gmx.us
> Rasmus <rasmus@gmx.us> writes:
> Maybe CalDav? There's a tool on F-droid called Tasks (or maybe Task) that
> can sync via DAVDroid to REPO.. Maybe org-caldav.el could be extended to
> support the sync. tasks between Org and REPO.
> Rasmus
hmm then each task have to get assigned to a date I guess? Despite that
I kind of like that solution, the name of the app is tasks btw but
there are 2 with that name in f-droid, the right one has a green
background and is lisensed under apache2 lisense.
I am not shure which solution I like more yours or the other todo.txt
solution somebody else posted here I have a bit of overhead
with the owncloud server, but 2way sync should work at least I read
something like that on the org-caldav.el site.
So it should actually work, I am just not shure about if I need a
date. I seldom (have to) force me into setting deadlines. So most of the
time its only tasks that I do when I have time and I am in the mood.
I guess maybe to test I could sync the caldav file manuelly one way to
test how I like the app/usecase. and when I like it and it works
reasonable well I can setup owncloud.
If I can put it some fake dates or leave them out it seems that would be
the better solution if the app is good enough.
Thx for that great suggestion!
next prev parent reply other threads:[~2016-01-17 2:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 19:59 backend for todo.txt format (todotxt.com) Stefan Huchler
2016-01-16 20:06 ` Rasmus
2016-01-17 2:21 ` Stefan Huchler [this message]
2016-01-17 11:47 ` Rasmus
2016-01-17 14:59 ` Stefan Huchler
2016-01-18 23:30 ` Rasmus
2016-01-19 4:31 ` Stefan Huchler
2016-01-17 4:56 ` Stefan Huchler
2016-01-16 20:28 ` Danie Roux
2016-01-19 5:51 ` Stefan Huchler
2016-01-19 5:59 ` Kyle Meyer
2016-01-19 6:15 ` Stefan Huchler
2016-01-19 6:20 ` Kyle Meyer
2016-02-02 17:11 ` Tim O'Callaghan
2016-01-16 22:30 ` 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=87wpr9uezv.fsf@jupiter.lan \
--to=stefan.huchler@mail.de \
--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).