From: "Saša Janiška" <gour@atmarama.com>
To: emacs-orgmode@gnu.org
Subject: org-class/diary-float entries do not sync (org-caldav)
Date: Wed, 22 Jun 2016 13:59:25 +0200 [thread overview]
Message-ID: <87h9clh1sy.fsf@atmarama.com> (raw)
Hello,
I’m trying to enter repeated tasks for e.g. daily language classes
during the month of July, daily (Mon-Frid) from 08:00-12:00 in my org
file and sync them via org-caldav to get them on my phone (synced with
OwnCloud with Davdroid app.
In the beginning I tried with the following:
** english class
<%%(org-class 2016 7 4 2016 7 29 2)> 08:00-12:00 english class
and the entry is added to my Agenda as:
gour-calendar:english class :gour::
but the time range is missing which can be ’fixed’ with:
** english class 08:00-12:00
<%%(org-class 2016 7 4 2016 7 29 2)>
which gives entry for Tuesdays during July as:
gour-calendar: 8:00-12:00 english class :gour::
The problem with the above is that it does not sync with
org-caldav-sync although it creates ID property.
Next thing I’ve tried is:
** english class
<%%(diary-float 7 1 1)>
and the only way to get time range is to use:
** english class 08:00-12:00
<%%(diary-float 7 1 1)>
but, again, the sync does not work and I also occasionaly run into
another problem - see this issue:
https://github.com/dengste/org-caldav/issues/91
By looking at org-caldav docs (https://github.com/dengste/org-caldav) it
looks that using org-class might be problematic indeed, but no idea why
the sync does not work with diary-float?
Moreover, there are several FAQs entries (http://orgmode.org/worg/org-faq.html)
showing similar/same examples and org-caldav docs says: „…If they are
inside an Org entry, there's a good chance they will be exported (see
below) and have an ID property, so they can be found by org-caldav…“, so
I’ll be grateful if someone can shed some light how to achieve the
desired result mentioned at the beginning?
Sincerely,
Gour
--
One who is able to withdraw his senses from sense objects,
as the tortoise draws its limbs within the shell,
is firmly fixed in perfect consciousness.
reply other threads:[~2016-06-22 11:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87h9clh1sy.fsf@atmarama.com \
--to=gour@atmarama.com \
--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 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.