all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Alexis <flexibeast@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Yak-shaving from org-caldav to url-dav.el
Date: Mon, 30 Jun 2014 19:15:10 +0200	[thread overview]
Message-ID: <87zjgub9pd.fsf@engster.org> (raw)
In-Reply-To: <87r426bpq7.fsf@gmail.com> (Alexis's message of "Mon, 30 Jun 2014 21:27:17 +1000")

Alexis writes:
> (1) Calling the `org-caldav-sync` command results in failure:
>
>> Got error status from PROPFIND: 
>> (("[calendar URL]" DAV:status 207 . " "))

I've added 207 as a valid PROPFIND result, so this should be fixed, but
will probably fail later on (I never tested it with DAViCal).

> One critical bit of code included in this version, but not in the
> 24.3.92 version of `url-dav.el`, are lines 420-423:
>
>     ;; This package was initially written for a different kind of
>     ;; QNAMES expansion, hence we have now to rewrite those so that
>     ;; for example ("DAV:" . "foo") becomes the symbol 'DAV:foo.
>     (url-dav-changexml (car tree))

That part was deemed to hackish and fixed in another way.

> Without this, HTTP 207 ("Multi-Status") responses from the CalDAV
> server aren't processed correctly, resulting in the "error status from
> PROPFIND" failure.

That's weird, since nothing but HTTP 200 should have been accepted.

> (2) So, let's "(load)" the randomsample version of `url-dav.el`. Doing
> so results in a new failure:

You cannot use that hacked url-dav together with newer Emacsen.

Please try the latest org-caldav version and let me know how it works
(on GitHub please, since this doesn't affect Emacs development).

-David



      reply	other threads:[~2014-06-30 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 11:27 Yak-shaving from org-caldav to url-dav.el Alexis
2014-06-30 17:15 ` David Engster [this message]

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=87zjgub9pd.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=emacs-devel@gnu.org \
    --cc=flexibeast@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.