From: David Engster <deng@randomsample.de>
To: Torsten Wagner <torsten.wagner@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: org-caldav feedback
Date: Tue, 22 Jan 2013 21:01:23 +0100 [thread overview]
Message-ID: <87boch2dik.fsf@engster.org> (raw)
In-Reply-To: <CAPaq-gP65LR0NcHsiy4ChYsNwjEnOUBWZ65BNZ6B6Eo_Q0TCng@mail.gmail.com> (Torsten Wagner's message of "Tue, 22 Jan 2013 16:35:13 +0100")
Torsten Wagner writes:
> I did not had time to play with the different parameters. For now I simply
> added all of them.
> I guess it has to do either with the timezone or with the daylight settings.
> Maybe you want to add this to a "How-to install for SOGo" as a workaround.
I think I found a better solution. I pushed a change to org-caldav which
allows to set org-icalendar-timezone to the string "UTC", which will put
events using universal time. The server should then transpose it to the
timezone you have set in your SOGo preferences. It works for me (for
SOGo, mind you; other calendar servers don't work well with that).
> One problem remain. If I change something in the caldav calendar, the time
> information in org get lost completely.
> E.g.
> * Meeting <2013-01-16 Wed 14:00>
> becomes
> * Meeting
> It subsitutes the right entry and hence I believe it gets the ID stuff right.
> However, it seems to have trouble to interpret the time information right (and
> ignore them?).
> If there is a way to help you debugging this please let me know.
My test suite runs fine with the SOGo server, so I'm guessing it has to
do with how you format your entries. Does this also happen when you put
the timestamp underneath the heading?
On a general note, I find manipulating Org entries rather delicate and
wonder why there are no helper functions to change things like headings,
timestamps, etc., which take care of the multitude of possibilities how
entries can be formatted. My guess is that org-elements might be the
solution for this, but I haven't looked at it yet...
-David
next prev parent reply other threads:[~2013-01-22 20:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 15:32 org-caldav feedback Torsten Wagner
2013-01-17 19:05 ` David Engster
2013-01-17 21:28 ` Torsten Wagner
2013-01-21 19:29 ` David Engster
2013-01-21 16:28 ` Torsten Wagner
2013-01-21 19:25 ` David Engster
2013-01-21 19:37 ` Torsten Wagner
2013-01-21 21:32 ` David Engster
2013-01-22 15:35 ` Torsten Wagner
2013-01-22 20:01 ` David Engster [this message]
2013-01-23 6:00 ` Eric S Fraga
2013-01-23 14:22 ` Torsten Wagner
2013-01-23 20:11 ` David Engster
2013-01-24 0:37 ` Eric S Fraga
2013-01-23 20:23 ` David Engster
2013-01-24 0:38 ` Eric S Fraga
2013-01-23 14:38 ` Torsten Wagner
2013-01-23 20:16 ` David Engster
2013-02-02 16:00 ` David Engster
2013-03-01 15:37 ` Torsten Wagner
2013-03-02 14:08 ` David Engster
2013-01-18 3:47 ` Eric S Fraga
2013-01-21 9:38 ` Christian Egli
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=87boch2dik.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-orgmode@gnu.org \
--cc=torsten.wagner@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 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).