emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Martin Beck <elwood151@web.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problems with org-export: "byte-code: Invalid function: 0"
Date: Fri, 8 Aug 2014 13:41:06 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140808T152310-102@post.gmane.org> (raw)
In-Reply-To: 87r40szixm.fsf@gmail.com

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

next prev parent reply	other threads:[~2014-08-08 13:41 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
2014-08-08  0:39     ` M
2014-08-08 13:41     ` Martin Beck [this message]
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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20140808T152310-102@post.gmane.org \
    --to=elwood151@web.de \
    --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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).