From: David Engster <deng@randomsample.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Julien Cubizolles <j.cubizolles@free.fr>
Subject: Re: org-caldav can't find org-prepare-agenda-buffers
Date: Wed, 06 Mar 2013 17:43:48 +0100 [thread overview]
Message-ID: <87vc944gxn.fsf@engster.org> (raw)
In-Reply-To: <871ubsfqcm.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 06 Mar 2013 17:24:57 +0100")
Nicolas Goaziou writes:
> Hello,
>
> David Engster <deng@randomsample.de> writes:
>
>> Julien Cubizolles writes:
>>> Bastien <bzg@altern.org> writes:
>>>
>>>> Achim Gratz <Stromeko@nexgo.de> writes:
>>>>
>>>>> I hope to put this together in the next week or
>>>>> so, then it will be possible to nuke all traces fr4om an old Org and
>>>>> then start from a clean slate with a new Org installation.
>>>>
>>>> Okay, thanks. Let us know how it goes,
>>>
>>> What temporary (as in every user fixing it locally) solution would you
>>> recommend to get org-caldav running in the mean time ?
>>
>> I just pushed a change which should fix this (if the new exporter is
>> compatible; I don't use Org from git).
>
> Interactive functions are usually not compatible between old export
> back-ends and new ones.
>
> What do you need from org-icalendar.el?
Only org-export-icalendar. As long as that one is producing the same
output, everything should be fine.
-David
next prev parent reply other threads:[~2013-03-06 16:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 10:34 org-caldav can't find org-prepare-agenda-buffers Julien Cubizolles
2013-02-27 14:12 ` Bastien
2013-02-27 19:18 ` David Engster
2013-02-27 22:30 ` Bastien
2013-02-28 6:57 ` David Engster
2013-02-28 7:38 ` Bastien
2013-02-28 16:17 ` David Engster
2013-02-28 18:25 ` Achim Gratz
2013-02-28 19:13 ` David Engster
2013-02-28 19:32 ` Achim Gratz
2013-03-02 11:17 ` Bastien
2013-03-02 13:26 ` David Engster
2013-03-02 17:18 ` Bastien
2013-03-02 20:17 ` Torsten Wagner
2013-03-03 12:26 ` David Engster
2013-03-04 10:46 ` Torsten Wagner
2013-03-02 22:19 ` Achim Gratz
2013-03-03 6:25 ` Bastien
2013-03-06 14:57 ` Julien Cubizolles
2013-03-06 16:15 ` David Engster
2013-03-06 16:24 ` Nicolas Goaziou
2013-03-06 16:43 ` David Engster [this message]
2013-03-06 17:08 ` Nicolas Goaziou
2013-03-06 17:22 ` David Engster
2013-03-06 17:32 ` Nicolas Goaziou
2013-03-06 21:24 ` David Engster
2013-03-07 9:13 ` Julien Cubizolles
2013-03-07 10:06 ` Vincent Beffara
2013-03-07 10:54 ` Nicolas Goaziou
2013-03-07 11:17 ` Vincent Beffara
2013-03-07 12:56 ` Nicolas Goaziou
2013-03-07 13:21 ` Vincent Beffara
2013-03-07 13:31 ` Vincent Beffara
2013-03-07 13:41 ` Vincent Beffara
2013-03-12 6:21 ` Julien Cubizolles
2013-03-12 10:18 ` Vincent Beffara
2013-03-12 20:31 ` David Engster
2013-03-14 0:05 ` Vincent Beffara
2013-03-06 16:51 ` Julien Cubizolles
2013-03-06 17:08 ` David Engster
2013-03-06 17:18 ` Julien Cubizolles
2013-03-06 18:35 ` David Engster
2013-03-02 11:19 ` Bastien
2013-03-02 13:33 ` David Engster
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=87vc944gxn.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-orgmode@gnu.org \
--cc=j.cubizolles@free.fr \
--cc=n.goaziou@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).