From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Babel related bug in elpa version 20121231 Date: Sat, 05 Jan 2013 11:51:59 -0700 Message-ID: <87k3rrh38w.fsf@gmail.com> References: <1342018996.75825.YahooMailNeo@web29804.mail.ird.yahoo.com> <8738ygbpvg.fsf@Rainer.invalid> <87mwworttu.fsf@Rainer.invalid> <87wqvrc2hu.fsf@bzg.ath.cx> <87bod3r2lo.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:33732) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TrYqh-0008Vd-E5 for emacs-orgmode@gnu.org; Sat, 05 Jan 2013 13:52:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TrYqg-0002nF-57 for emacs-orgmode@gnu.org; Sat, 05 Jan 2013 13:52:03 -0500 Received: from mail-ia0-f172.google.com ([209.85.210.172]:56799) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TrYqf-0002nB-TG for emacs-orgmode@gnu.org; Sat, 05 Jan 2013 13:52:02 -0500 Received: by mail-ia0-f172.google.com with SMTP id z13so14974198iaz.3 for ; Sat, 05 Jan 2013 10:52:01 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org 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 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/.org and a ~/.emacs.d/.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 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