From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Undefined variable: org-babel-execute-src-block-maybe Date: Mon, 01 Aug 2011 10:18:57 -0500 Message-ID: <874o21duse.fsf@fastmail.fm> References: <878vrddwfv.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:33731) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QnuGj-0007XZ-Ay for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 11:19:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QnuGh-00022z-U2 for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 11:19:01 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:59866) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QnuGh-00022v-Nh for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 11:18:59 -0400 In-Reply-To: (John Hendy's message of "Mon, 1 Aug 2011 09:59:33 -0500") 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: John Hendy Cc: Org Mode John Hendy writes: > On Mon, Aug 1, 2011 at 9:43 AM, Matt Lundin wrote: >> With the latest git, I get the following message when I try to follow a >> link in org-mode: >> >> org-babel-execute-src-block-maybe: Symbol's value as variable is void: org-babel-inline-src-block-regexp >> >> The problem goes away if I reload org files with M-x org-reload. >> >> Note: I normally run org-mode from byte-compiled files. I.e., I type >> "make clean && make" when updating a file. > > For reference to others responding, this has come up twice already in > the recent days: > - Same C-c C-o problem, reported by Hsiu-Khuern Tang > --- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg44896.html > > - Unable to export footnotes in LaTeX, reported by me > --- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg44895.html > > Both were traced to the same commit, same error message, and same workarounds: > - M-x org-reload with an up to date git pull > - Don't actually make the up to date git pull (or make clean after make) > - Revert back to release_7.7 > O.K. Thanks. I'll await Eric's decision. Best, Matt