From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: BUG: Export images to LaTeX Date: Sat, 22 Oct 2011 10:12:18 -0400 Message-ID: <87bot9ktdp.fsf@norang.ca> References: <2901336D-F5F2-430B-84C8-8E903FEFE7FB@yahoo.com> <12962.1319239571@alphaville.americas.hpqcorp.net> <3D666319-4172-428D-9622-7B912B2AD6C7@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:35846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHcJF-0008TD-9n for emacs-orgmode@gnu.org; Sat, 22 Oct 2011 10:12:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RHcJD-0007Lq-4x for emacs-orgmode@gnu.org; Sat, 22 Oct 2011 10:12:25 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:60457) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHcJD-0007Lm-1n for emacs-orgmode@gnu.org; Sat, 22 Oct 2011 10:12:23 -0400 In-Reply-To: <3D666319-4172-428D-9622-7B912B2AD6C7@yahoo.com> (Anthony Lander's message of "Sat, 22 Oct 2011 07:53:44 -0400") 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: Anthony Lander Cc: nicholas.dokos@hp.com, emacs-orgmode Mode Anthony Lander writes: > On 11-Oct-21, at 7:26 PM, Nick Dokos wrote: > >> Anthony Lander wrote: >> >>> I've run into a strange problem with the latest org pull. Exporting >>> inlined images with the LaTeX exporter works or not depending on >>> whether I include org-jsinfo in org-modules(!). This is with emacs >>> -q on the 24.0.90.1 emacs recent release. >>> >>> Can someone please try to reproduce this to confirm? >> >> Pretty weird - I can reproduce this by omitting org-jsinfo from org-modules and >> starting with a minimal .emacs. > > Thanks for reproducing this. It is indeed weird, as you describe below. > > Unfortunately, I pull infrequently, so I can't really narrow down when it started happening. > > -Anthony You can use git bisect to identify the commit that caused the breakage. ORIG_HEAD should point at the commit you used to be on before your last pull. -Bernt