From mboxrd@z Thu Jan 1 00:00:00 1970 From: Justin Gordon Subject: Re: mixed orgmode installation Date: Fri, 3 Jan 2014 08:08:06 -1000 Message-ID: References: <87a9jshdpi.fsf@gmail.com> <20130904150749.GA12670@kuru.dyndns-at-home.com> <1378618836.1967.4.camel@ahc> <20130908151042.GH20690@kuru.dyndns-at-home.com> <878uz7s1au.fsf@Rainer.invalid> <20140103084300.7b7cebb5@london> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c30a68ef950604ef14cb47 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39895) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz9Ab-0006YU-8T for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 13:08:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vz9AZ-0003oK-K3 for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 13:08:29 -0500 Received: from mail-ob0-x235.google.com ([2607:f8b0:4003:c01::235]:58447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz9AZ-0003oB-DV for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 13:08:27 -0500 Received: by mail-ob0-f181.google.com with SMTP id uy5so15543340obc.26 for ; Fri, 03 Jan 2014 10:08:26 -0800 (PST) In-Reply-To: <20140103084300.7b7cebb5@london> 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: Sharon Kimble Cc: emacs-orgmode@gnu.org --001a11c30a68ef950604ef14cb47 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable My problem was because I had a line (require 'org-publish) It would be super if there was a way to clearly flag this as an error after an upgrade. Maybe renamed files should have old skeleton files that produce an error indicating the new file name? On Thu, Jan 2, 2014 at 10:43 PM, Sharon Kimble wrot= e: > On Thu, 2 Jan 2014 08:06:46 +0000 (UTC) > Justin Gordon wrote: > > > Achim Gratz nexgo.de> writes: > > > > > > > > John Hendy writes: > > > > Then again, is Worg saying that if `M-x org-version` outputs the > > > > "correct" answer... we're all set and there's nothing to worry > > > > about? > > > > > > The output of org-version is determined essentially by checking for > > > two files from the installation and comparing where they would be > > > loaded from. This catches the most common problems, but certainly > > > not all. In particular, it won't see when the load-path has been > > > changed after some parts of Org have already been loaded from > > > someplace else (but org-reload will give a warning for this case). > > > > > > Regards, > > > Achim. > > > > > > If I byte compile a file, I get this message: > > In org-jekyll-publish-to-html: > > ox-jekyll.el:280:4:Warning: org-publish-org-to called with 5 > > arguments, but accepts only 4 > > > > This is because my installation is pointing to the emacs default > > version rather than my version from git. If I do C-h f and look up > > this function, I get pointed to the emacs default version. > > > > However, if I do org-version, I get the proper new version. > > > > However, if I do list-load-path-shadows, I can verify that > > org-publish is not shadowed, and that's probably due to the fact that > > the new file is called ox-publish. > > > > How do I fix this??? > > > > > > I've tried > > You=92ve tried what? You seem to have cut off in mid-sentence. > > I had the same problem on debian testing which I resolved by removing > the debian version and going solely with the one from ELPA, in your > case from git. I'm pretty sure that the git version will be more > up-to-date than your distro version! :) > > Sharon. > -- > A taste of linux =3D http://www.sharons.org.uk > efever =3D http://www.efever.blogspot.com/ > efever =3D http://sharon04.livejournal.com/ > my git repo =3D https://bitbucket.org/boudiccas/dots > Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.4.2 > Registered Linux user 561944 > --=20 Justin Gordon | 808-877-6461 | m: 808-281-7272 www.railsonmaui.com | twitter: @railsonmaui | sugarranchmaui.com | Sugar Ranch Blog --001a11c30a68ef950604ef14cb47 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
My problem was because I had a line=A0

= =A0 =A0 (require 'org-publish)

It would be sup= er if there was a way to clearly flag this as an error after an upgrade. Ma= ybe renamed files should have old skeleton files that produce an error indi= cating the new file name?



O= n Thu, Jan 2, 2014 at 10:43 PM, Sharon Kimble <boudiccas@talktalk.net= > wrote:
On Thu, 2 Jan 2014 08:06:46 +0000 (UTC)
Justin Gordon <justin.gordon@= gmail.com> wrote:

> Achim Gratz <Stromeko <at> nexgo.de> writes:
>
> >
> > John Hendy writes:
> > > Then again, is Worg saying that if `M-x org-version` outputs= the
> > > "correct" answer... we're all set and there= 9;s nothing to worry
> > > about?
> >
> > The output of org-version is determined essentially by checking f= or
> > two files from the installation and comparing where they would be=
> > loaded from. =A0This catches the most common problems, but certai= nly
> > not all. =A0In particular, it won't see when the load-path ha= s been
> > changed after some parts of Org have already been loaded from
> > someplace else (but org-reload will give a warning for this case)= .
> >
> > Regards,
> > Achim.
>
>
> If I byte compile a file, I get this message:
> In org-jekyll-publish-to-html:
> ox-jekyll.el:280:4:Warning: org-publish-org-to called with 5
> arguments, but accepts only 4
>
> This is because my installation is pointing to the emacs default
> version rather than my version =A0from git. If I do C-h f and look up<= br> > this function, I get pointed to the emacs default version.
>
> However, if I do org-version, I get the proper new version.
>
> However, if I do list-load-path-shadows, I can verify that
> org-publish is not shadowed, and that's probably due to the fact t= hat
> the new file is called ox-publish.
>
> How do I fix this???
>
>
> I've tried

You=92ve tried what? You seem to have cut off in mid-sentence.

I had the same problem on debian testing which I resolved by removing
the debian version and going solely with the one from ELPA, in your
case from git. I'm pretty sure that the git version will be more
up-to-date than your distro version! :)

Sharon.
--
A taste of linux =3D http://www.sharons.org.uk
efever =3D ht= tp://www.efever.blogspot.com/
efever =3D h= ttp://sharon04.livejournal.com/
my git repo =3D https://bitbucket.org/boudiccas/dots
Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.4.2
Registered Linux user 561944



--
Justin Gordon |=A0808-877-6461 |=A0m: 808-281-7272<= /div>
--001a11c30a68ef950604ef14cb47--