Problems with org-export: "byte-code: Invalid function: 0"

Problems with org-export: "byte-code: Invalid function: 0"

[Martin Beck]

[-- Attachment #1: Type: text/html, Size: 1361 bytes --]

Re: Problems with org-export: "byte-code: Invalid function: 0"

[Nick Dokos]

"Martin Beck" <Elwood151@web.de> writes:

> I'm doing my first steps trying to publish my org-mode content to HTML and it seems that there is something that causes problems
> with publishing.
>  
> I tracked it down to this paragraph which seems to cause the problem:
>   _____  
> Connect at AIIM is a news communication provided by AIIM. 2014
> AIIM - The Global Community of Information Professionals
> 1100 Wayne Avenue, Suite 1100, Silver Spring, MD 20910 USA
> Phone: 301-587-8202 resource://skype_ff_extension-at-jetpack/skype_ff_extension/data/call_skype_logo.png301-587-8202
> The IT Centre, 8 Canalside, Lowesmoor Wharf, Worcestershire, WR1 2RR  UK
> Tel: +44 (0) 1905 727600 resource://skype_ff_extension-at-jetpack/skype_ff_extension/data/call_skype_logo.png+44 (0) 1905 727600
>   _____  
>  
> (in my org-mode document, the linebreaks are visible only as ^M)
>  
> Can somebody tell me what's the problem here?
> When trying C-c C-e h o
> I get this error message: "Invalid function: 0"
>  

This may be a problem in your setup.  Please set the variable
debug-on-error to t, try to publish and post the resulting backtrace.

Alternatively, try restarting your emacs: it may have acquired a setting
inadvertently that causes problems. You might also try without most of
your customizations (emacs -q), but loading a minimal file that just
sets up org and the publishing project.

Nick

Re: Problems with org-export: "byte-code: Invalid function: 0"

[Martin Beck]

[-- Attachment #1: Type: text/html, Size: 6442 bytes --]

Re: Problems with org-export: "byte-code: Invalid function: 0"

[Nick Dokos]

"Martin Beck" <Elwood151@web.de> writes:

> Nick Dokos <ndokos <at> gmail.com> writes:
>>
>> "Martin Beck" <Elwood151 <at> web.de> writes:
>> > I tracked it down to this paragraph which seems to cause
>> > the problem:
>> >   _____  
>> > Connect at AIIM is a news communication provided by AIIM. 2014
>> > AIIM - The Global Community of Information Professionals
>> > 1100 Wayne Avenue, Suite 1100, Silver Spring, MD 20910 USA
>> > Phone: 301-587-8202
> resource://skype_ff_extension-at-jetpack/skype_ff_extension/data/call_skype_logo.png301-587-8202
>> > The IT Centre, 8 Canalside, Lowesmoor Wharf, Worcestershire,
> WR1 2RR  UK
>> > Tel: +44 (0) 1905 727600
>>
> resource://skype_ff_extension-at-jetpack/skype_ff_extension/data/call_skype_logo.png+44
>> (0) 1905 727600
>> >   _____  
>> >  
>> > (in my org-mode document, the linebreaks are visible only as ^M)
>> >  
>> >  
>>
>> This may be a problem in your setup.  Please set the variable
>> debug-on-error to t, try to publish and post the resulting backtrace.
>>
>> Alternatively, try restarting your emacs: it may have acquired a
>> setting
>> inadvertently that causes problems. You might also try without most
>> of
>> your customizations (emacs -q), but loading a minimal file that just
>> sets up org and the publishing project.
>>
>> Nick
>>
>>
> Hi Nick,
> I restarted emacs several times in the meantime - no effect.
> I then started emacs with option -q from cygwin,
> then opened the document,
> did M-x org-mode RET
> and the export.
> The debugger says:
> Debugger·entered--Lisp·error:·(invalid-function·0)$
> ··(0)$
> ··eval((0))$
> ··org-babel-read("(0)")$
> ··org-babel-ref-parse("results=(0)")$
> ··#[(el)·"^HA:\203»     ^@^HA\207\301^HA!\207"·$
> [el·org-babel-ref-parse]·2]((:var·.·"results=(0)"))$
> ··mapcar(#[(el)·"^HA:\203»      ^@^HA\207\301^HA!\207"·$
> [el·org-babel-ref-parse]·2]·((:var·.·"results=(0)")))$
> ··org-babel-process-params(((:comments·.·"")·(:shebang·.·"")·$
> (:cache·.·"no")·(:padline·.·"")·(:noweb·.·"no")·(:tangle·.·"no")·$
> (:exports·.·"results")·(:results·.·"replace")·(:var·.·"results=(0)")·$
> (:session·.·"none")·(:hlines·.·"no")·(:padnewline·.·"yes")))$
> ··org-babel-exp-results(("emacs-lisp"·"results"·((:comments·.·"")·$
> (:shebang·.·"")·(:cache·.·"no")·(:padline·.·"")·(:noweb·.·"no")·$
> (:tangle·.·"no")·(:exports·.·"results")·(:results·.·"replace")·$
> (:var·.·"results=(0)")·(:padnewline·.·"yes")·(:hlines·.·"no")·$
> (:session·.·"none"))·""·nil·163)·lob·nil·nil)$
> ··org-babel-exp-do-export(("emacs-lisp"·"results"·((:comments·.·"")·$
> (:shebang·.·"")·(:cache·.·"no")·(:padline·.·"")·(:noweb·.·"no")·$
> (:tangle·.·"no")·(:exports·.·"results")·(:results·.·"replace")·$
> (:var·.·"results=(0)")·(:padnewline·.·"yes")·(:hlines·.·"no")·$
> (:session·.·"none"))·""·nil·163)·lob)$
> ··org-babel-exp-non-block-elements(1·3532)$              <<<<<<<<<<<<<<<<<<<<<<<
> ··org-babel-exp-process-buffer()$
> ··org-export-execute-babel-code()$
> ··org-export-as(html·nil·nil·nil·nil)$
> ··org-export-to-file(html·"./test.html"·nil·nil·nil·nil)$
> ··org-html-export-to-html(nil·nil·nil·nil)$
> ··(org-open-file·(org-html-export-to-html·nil·s·v·b))$
> ··(if·a·(org-html-export-to-html·t·s·v·b)·(org-open-file·$
> (org-html-export-to-html·nil·s·v·b)))$
> ··(lambda·(a·s·v·b)·(if·a·(org-html-export-to-html·t·s·v·b)·$
> (org-open-file·(org-html-export-to-html·nil·s·v·b))))(nil·nil·nil·nil)$
> ··org-export-dispatch(nil)$
> ··call-interactively(org-export-dispatch·nil·nil)$

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.

-- 
Nick

Re: Problems with org-export: "byte-code: Invalid function: 0"

[M]

> Von: Nick Dokos <ndokos@gmail.com>
> Datum: Thu, 07 Aug 2014 06:35:17 -0400
> An: <emacs-orgmode@gnu.org>
> Betreff: Re: [O] Problems with org-export: "byte-code: Invalid function: 0"
> 
> "Martin Beck" <Elwood151@web.de> writes:
> 
>> Nick Dokos <ndokos <at> 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'm using org-mode 8.2.7c.
I suspect, that you would call that "recent org", so I wonder how the old
code could come into my installation.
But I'll have a look tomorrow.
Is there a way to find the source of this old code within Emacs?

Kind regards

Martin

Re: Problems with org-export: "byte-code: Invalid function: 0"

[Martin Beck]

Nick Dokos <ndokos <at> 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?

Kind regards

Martin

Kind regards

Martin

Re: Problems with org-export: "byte-code: Invalid function: 0"

[Nick Dokos]

Martin Beck <elwood151@web.de> writes:

> Nick Dokos <ndokos <at> 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