From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Undefined variable: org-babel-execute-src-block-maybe Date: Mon, 1 Aug 2011 09:59:33 -0500 Message-ID: References: <878vrddwfv.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:57247) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qntxw-0006oK-Iw for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 10:59:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qntxu-0005xR-Vd for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 10:59:36 -0400 Received: from mail-ey0-f174.google.com ([209.85.215.174]:64817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qntxu-0005wo-Lm for emacs-orgmode@gnu.org; Mon, 01 Aug 2011 10:59:34 -0400 Received: by eyx24 with SMTP id 24so7532664eyx.19 for ; Mon, 01 Aug 2011 07:59:33 -0700 (PDT) In-Reply-To: <878vrddwfv.fsf@fastmail.fm> 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: Matt Lundin Cc: Org Mode 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 Best regards, John > > Best, > Matt > >