From: Nick Dokos <nicholas.dokos@hp.com>
To: Luke Crook <luke@balooga.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode 7.9.4 now returns org-strip-protective-commas
Date: Fri, 22 Mar 2013 16:54:40 -0400 [thread overview]
Message-ID: <6002.1363985680@alphaville> (raw)
In-Reply-To: Message from Luke Crook <luke@balooga.com> of "Fri, 22 Mar 2013 20:17:35 -0000." <loom.20130322T210928-883@post.gmane.org>
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
next prev parent reply other threads:[~2013-03-22 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 20:17 org-mode 7.9.4 now returns org-strip-protective-commas Luke Crook
2013-03-22 20:54 ` Nick Dokos [this message]
2013-03-25 17:45 ` Luke Crook
2013-03-28 22:46 ` Luke Crook
2013-03-22 20:55 ` Luke Crook
2013-03-22 21:01 ` Bastien
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=6002.1363985680@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=luke@balooga.com \
/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.