Re: Babel related bug in elpa version 20121231

[Eric Schulte <schulte.eric@gmail.com>]

After reading the first post in this thread, it seems that the problem
is likely caused by this commit [1], which changes the syntax of valid
code blocks.  This means that an Org-mode file with certain types of
code blocks may either be valid before the commit, or valid after the
commit, but not both.

Achim Gratz <Stromeko@nexgo.de> writes:

> Robert Horn writes:
>> All of my problems seem to arise from the bad interactions between
>> starting with the built-in package version of org that is used by the
>> org-babel-load-file, and then transitioning part way through its
>> execution of the starter-kit.org to the elpa updated version of org.
>> The result is much like a mixed version install of org.  Strange things
>> go wrong.
>
> This may provoke a different mode of failure, but maybe you could try to
> add a "(package-initialize)" at the beginning of your ~/init.el.
>

That sounds like it should work, although I would go with the more
complete but possibly overkill

    ;; emacs-lisp
    (package-initialize)
    (require 'org)
    (org-reload)

Let me know if either of the above is sufficient to solve your problem
and ensure that only the latest ELPA version of Org-mode is used through
the entire startup process.  If so I will add this to the starter kit.

>
>> I like having the nicely formatted and documented setup that I get with
>> an export to html of the org files that contain the startup scripts. My
>> intended mode of operation is to have a customized set of starterkit.org
>> files that can apply to everyone, with each user also having a
>> ~/.emacs.d/<user>.org and a ~/.emacs.d/<machine>.org to provide further
>> user customizations, including per machine variations for users who need
>> different setups on different machines.
>
> Again, I understand the appeal of starterkit, I just aren't too enamored
> with its insistence to run through the Org files each time (but I may
> not understand why it needs to do that).  IMHO, if it were tangling to
> elisp, then these problems might not even exist.
>

The starter kit does not "run through the Org files each time", rather
it tangles the .org files to .el files, and then on all subsequent loads
it loads directly from the .el files (unless the .org file is newer).

Cheers -- Eric

Footnotes: 
[1] 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.

-- 
Eric Schulte
http://cs.unm.edu/~eschulte