org-mode 7.9.4 now returns org-strip-protective-commas

org-mode 7.9.4 now returns org-strip-protective-commas

[Luke Crook]

I updated org-mode to 7.9.4, and now a I receive the following error from Emacs 
when I try to generate Latex output;

Code block evaluation complete.
org-export-select-backend-specific-text: Symbol's function definition is void: 
org-strip-protective-commas



Any ideas what might be going on?

Re: org-mode 7.9.4 now returns org-strip-protective-commas

[Nick Dokos]

Luke Crook <luke@balooga.com> wrote:

> I updated org-mode to 7.9.4, and now a I receive the following error from Emacs 
> when I try to generate Latex output;
> 
> Code block evaluation complete.
> org-export-select-backend-specific-text: Symbol's function definition is void: 
> org-strip-protective-commas
> 
> 
> 
> Any ideas what might be going on?
> 
> 
> 

My guess is that  you have a seriously mixed-up installation.

org-strip-protective-commas was removed on Sept. 30, 2012 with
this commit and at the same time org-export-select-backend-specific-text
was modified to use the new function org-unescape-code-in-region:

,----
| commit fac86b03fe19d5bb6fe018c3cbc3becac6263b0e
| Author: Nicolas Goaziou <n.goaziou@gmail.com>
| Date:   Sun Sep 30 17:20:27 2012 +0200
| 
|     Normalize comma-escaping of src-blocks and example-blocks
|     
|     * lisp/org-src.el (org-escape-code-in-string,
|       org-unescape-code-in-string, org-escape-code-in-region,
|       org-unescape-code-in-region): New functions.
|     (org-edit-src-code, org-edit-src-exit): Use new functions.
|     * lisp/org.el (org-strip-protective-commas): Removed function.
|     * lisp/org-exp.el (org-export-select-backend-specific-text): Use new
|       function.
|     * lisp/ob.el (org-babel-parse-src-block-match,
|       org-babel-parse-inline-src-block-match, org-babel-insert-result):
|       Always escape produced blocks, independently on the language of the
|       block, if any.  Use new functions.
|     * doc/org.texi: Update documentation.
|     * testing/lisp/test-ob.el: Update test.
`----

So the fact that your org-export-select-backend-specific-text calls
org-strip-protective-commas means that you are picking up an old
org-exp.el, and the fact that the latter is missing means that you are
picking up a new org.el.

I hope that's enough to let you figure it out, because beyond that
my crystal ball is completely opaque. If you need more help, you will
need to provide more detail: emacs and org versions and enough of your
setup to be able to see what's going on.

Also try to figure out from which file(s) these things are loaded.
My usual method is M-x locate-library but M-x list-load-path-shadows
may be a better way to go.

Nick

Re: org-mode 7.9.4 now returns org-strip-protective-commas

[Luke Crook]

Nick Dokos <nicholas.dokos <at> hp.com> writes:

> 
> My guess is that  you have a seriously mixed-up installation.
>

That's what org-version just told me.  I downloaded the latest version of Emacs 
for windows which includes org-mode v7.9.3f.  I'll try start from there.

///Luke

Re: org-mode 7.9.4 now returns org-strip-protective-commas

[Luke Crook]

[-- Attachment #1: Type: text/plain, Size: 324 bytes --]

On Fri, Mar 22, 2013 at 1:54 PM, Nick Dokos <nicholas.dokos@hp.com> wrote:
>
>
> My guess is that  you have a seriously mixed-up installation.



It was a load-path problem.  I use an init.el file to load my ~/.emacs.d/
emacs.org initialization file, and I totally forgot to update the path to
the org directory in init.el.

[-- Attachment #2: Type: text/html, Size: 769 bytes --]

Re: org-mode 7.9.4 now returns org-strip-protective-commas

[Luke Crook]

Luke Crook <luke <at> balooga.com> writes:

I also see the following error in 7.9.4;

Code block evaluation complete.
progn: Symbol's function definition is void: org-unescape-code-in-region

Re: org-mode 7.9.4 now returns org-strip-protective-commas

[Bastien]

Hi Luke,

Luke Crook <luke@balooga.com> writes:

> I updated org-mode to 7.9.4

If you updated through git, don't forget to make 

~$ make autoloads

or simply

~$ make

if you want to compile Org.

If you updated by downloading a .zip/.tar.gz file, make sure the
load-path is set correctly.

See http://orgmode.org/org.html#Installation for details.

HTH,

-- 
 Bastien