From mboxrd@z Thu Jan 1 00:00:00 1970 From: Torsten Wagner Subject: Re: org-caldav can't find org-prepare-agenda-buffers Date: Mon, 4 Mar 2013 11:46:41 +0100 Message-ID: References: <87k3puyri0.fsf@free.fr> <871uc1sv4s.fsf@bzg.ath.cx> <87vc9d36qp.fsf@engster.org> <87lia9o0e9.fsf@bzg.ath.cx> <878v692ae0.fsf@engster.org> <87621cj3bc.fsf@bzg.ath.cx> <874ngw2z26.fsf@engster.org> <87txoum4pe.fsf@bzg.ath.cx> <87y5e66igm.fsf@engster.org> <87zjyl3ck6.fsf@bzg.ath.cx> <2dd4013d-f27b-4303-8834-4906715ec412@email.android.com> <878v647jpv.fsf@engster.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b6050de7e2aa404d717127f Return-path: Received: from eggs.gnu.org ([208.118.235.92]:50149) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCSuq-0000IV-OT for emacs-orgmode@gnu.org; Mon, 04 Mar 2013 05:46:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCSuo-0000Y3-CA for emacs-orgmode@gnu.org; Mon, 04 Mar 2013 05:46:44 -0500 Received: from mail-ee0-f54.google.com ([74.125.83.54]:55408) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCSuo-0000Xw-3P for emacs-orgmode@gnu.org; Mon, 04 Mar 2013 05:46:42 -0500 Received: by mail-ee0-f54.google.com with SMTP id c41so3697734eek.27 for ; Mon, 04 Mar 2013 02:46:41 -0800 (PST) In-Reply-To: <878v647jpv.fsf@engster.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Torsten Wagner , Bastien , Org Mode Mailing List , Julien Cubizolles --047d7b6050de7e2aa404d717127f Content-Type: text/plain; charset=ISO-8859-1 Hi David, Well it would be a temporary solution for two reasons. 1. New emacs releases would come with the new org-files. 2. All third-party code might by time move to the new files. Thus, I thought this is a (maybe on a long perspective) temporary solution. Other non-unix like OSes: In that case, a small wrapper file, which replaces the old files might be the best solution, since it would work under all OSes. This wrapper could call the right functions within the new file and issues a warning/error/log that the call is deprecated. Hence it gives third-party maintainers (or anyone who jumps in) enough time to change the code. On 3 March 2013 13:26, David Engster wrote: > Torsten Wagner writes: > > I didn't follow this thread in detail. But shouldn't it be enough to > symlink > > e.g. org-icalendar against ox-icalendar. As far as I understood emacs > would > > prioritize those local symlinks over the system wide installation. This > would > > be a temporary solution until a new emacs release. > > Why temporary? What about people installing Org 8.x on older Emacsen? > > > Actually, under Linux, this is a pretty common way to bend > > dependencies towards the newest version of a lib. Not sure for > > windows users. > > Won't work on MS-DOS, and on Windows it is highly problematic for > various reasons (they're called "junctions" there; you need > administrator privileges to create them, and the upcoming Emacs 24.3 > will be the first version to even support them). > > -David > --047d7b6050de7e2aa404d717127f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi David,

Well it would be a temporary = solution for two reasons.
1. New emacs releases would come with t= he new org-files.
2. All third-party code might by time move to t= he new files.
Thus, I thought this is a (maybe on a long perspective) temporary solu= tion.

Other non-unix like OSes:
In that case, = a small wrapper file, which replaces the old files might be the best soluti= on, since it would work under all OSes. This wrapper could call the right f= unctions within the new file and issues a warning/error/log that the call i= s deprecated. Hence it gives third-party=A0maintainers=A0(or anyone who jum= ps in) enough time to change the code.=A0


O= n 3 March 2013 13:26, David Engster <deng@randomsample.de> wrote:
Torsten Wagner writes:
> I didn't follow this thread in detail. But shouldn't it be eno= ugh to symlink
> e.g. org-icalendar against ox-icalendar. As far as I understood emacs = would
> prioritize those local symlinks over the system wide installation. Thi= s would
> be a temporary solution until a new emacs release.

Why temporary? What about people installing Org 8.x on older Emacsen?=

> Actually, under Linux, this is a pretty common way to bend
> dependencies towards the newest version of a lib. =A0Not sure for
> windows users.

Won't work on MS-DOS, and on Windows it is highly problematic for=
various reasons (they're called "junctions" there; you need administrator privileges to create them, and the upcoming Emacs 24.3
will be the first version to even support them).

-David

--047d7b6050de7e2aa404d717127f--