From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Problems with org-export: "byte-code: Invalid function: 0" Date: Fri, 08 Aug 2014 10:04:08 -0400 Message-ID: <87tx5nulgn.fsf@alphaville.bos.redhat.com> References: <87r40szixm.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XFkmW-0002lJ-I6 for emacs-orgmode@gnu.org; Fri, 08 Aug 2014 10:04:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XFkmQ-0008K8-CX for emacs-orgmode@gnu.org; Fri, 08 Aug 2014 10:04:32 -0400 Received: from plane.gmane.org ([80.91.229.3]:35926) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XFkmQ-0008JZ-67 for emacs-orgmode@gnu.org; Fri, 08 Aug 2014 10:04:26 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XFkmO-0004ri-GB for emacs-orgmode@gnu.org; Fri, 08 Aug 2014 16:04:24 +0200 Received: from pool-173-48-174-104.bstnma.fios.verizon.net ([173.48.174.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Aug 2014 16:04:24 +0200 Received: from ndokos by pool-173-48-174-104.bstnma.fios.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 08 Aug 2014 16:04:24 +0200 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: emacs-orgmode@gnu.org Martin Beck writes: > Nick Dokos gmail.com> writes: > > >> >> This shows a problem evaluating a babel #+call or an inline source block >> somewhere between positions 1 and 3532 in the buffer. I suspect those >> call_skype thingies in your text are misinterpreted as babel calls >> somehow. >> >> The thing is that org-babel-exp-non-block-elements does not exist any >> longer: it was taken out last December (from both master and maint). >> With recent org, I don't have a problem exporting your text, so my >> suggestion is: upgrade. >> > > Hi Nick, > > thanks a lot for your help! I just installed org-mode 8.2.7c, > so in general, I think I should not have this problem. > > Org-mode version 8.2.7c (8.2.7c-dist @ > c:/Users/myaccount/Documents/mypath/org-mode/org_current/lisp/) > > I launched emacs -q from cygwin terminal, then did org-version > which said "N/A" and found that there seemed to be some org-files in > /usr/share/emacs/site-lisp/org > and some in /usr/share/emacs/24.3/lisp/org > > I removed both directories with their content, but I still have > the problem during export. > I can only avoid it, if i change the text in the org file, e. g. by > removing the "c" from "call_", so that it just leaves "all_". > Then the export works without a problem. > > So my question is: how can I track down the component (which should not be > in my system) that causes this problem? > Yes, it seems that you are picking up an older version (probably the one that got bundled with your emacs). These things depend on how you install your org in general. At the very least however, you *must* load an init file that sets your load-path appropriately, when you do emacs -q (a so-called "minimal .emacs" - search the list for some examples): emacs -q -l /path/to/minimal/.emacs If you use ELPA to install org, you need to do (package-initialize) as the very first thing in your init file (and iiuc, this takes care of setting load-path appropriately). See Achim's posts in reply to Salome on the ML (recently - within the past week). I don't use ELPA so I hope somebody will chime in here if this is wrong. See also http://orgmode.org/elpa.html for more information. I also don't use Windows/cygwin, so there might be complications here that I'm not aware of. -- Nick