From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Problems with org-export: "byte-code: Invalid function: 0"
Date: Thu, 07 Aug 2014 06:35:17 -0400 [thread overview]
Message-ID: <87r40szixm.fsf@gmail.com> (raw)
In-Reply-To: trinity-b00915ae-e031-4316-bef8-9e8f3a64df0e-1407401764750@3capp-webde-bs48
"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
next prev parent reply other threads:[~2014-08-07 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 14:46 Problems with org-export: "byte-code: Invalid function: 0" Martin Beck
2014-08-05 16:09 ` Nick Dokos
2014-08-07 8:56 ` Martin Beck
2014-08-07 10:35 ` Nick Dokos [this message]
2014-08-08 0:39 ` M
2014-08-08 13:41 ` Martin Beck
2014-08-08 14:04 ` Nick Dokos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r40szixm.fsf@gmail.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.