From: Bernt Hansen <firstname.lastname@example.org>
To: Anthony Lander <email@example.com>
Cc: firstname.lastname@example.org, emacs-orgmode Mode <email@example.com>
Subject: Re: BUG: Export images to LaTeX
Date: Sat, 22 Oct 2011 10:12:18 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <3D666319-4172-428D-9622-7B912B2AD6C7@yahoo.com> (Anthony Lander's message of "Sat, 22 Oct 2011 07:53:44 -0400")
Anthony Lander <email@example.com> writes:
> On 11-Oct-21, at 7:26 PM, Nick Dokos wrote:
>> Anthony Lander <firstname.lastname@example.org> 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 22.214.171.124 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.
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
next prev parent reply other threads:[~2011-10-22 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 21:22 BUG: Export images to LaTeX Anthony Lander
[not found] ` <email@example.com>
2011-10-22 11:53 ` Anthony Lander
2011-10-22 14:12 ` Bernt Hansen [this message]
2011-10-22 14:21 ` Jambunathan K
2011-10-22 19:45 ` Nick Dokos
2011-10-22 13:42 ` Bastien
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).