From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: problem exporting latex fragments to html: Debian's dvipng 1.12-1 is buggy
Date: Wed, 3 Feb 2010 16:14:52 +0100 [thread overview]
Message-ID: <DD9B6B08-57C1-4DD3-8B3D-46DB994CF28B@gmail.com> (raw)
In-Reply-To: <874olz3flq.wl%ucecesf@ucl.ac.uk>
Hi Eric,
OK, this now throws an error.
- Carsten
On Feb 2, 2010, at 2:57 PM, Eric S Fraga wrote:
> Hi,
>
> I'm obviously having a bad two days with org-mode but, this time, I've
> actually solved the problem myself. I thought I would highlight the
> issue in case anybody else runs into this.
>
> Short summary: exporting org files with latex fragments to HTML failed
> to create the images. I tracked the problem down to dvipng failing
> (memory reference problems). My system is Debian with a mixture of
> testing and unstable (yes, this will do it to you every time!). In
> any case, version 1.12-1 of dvipng seems to have problems; the latest
> in testing is 1.12-3 and this one works.
>
> However, I thought I would bring up a minor point: the failure to
> create images was not obvious; I had to resort to going through my
> *Messages* buffer. I then tried toggling debug on error to see why
> the image creation was failing but this had no effect as an error
> condition is not raised; this begs the question: should an error
> condition be raised when an image creation fails?
>
> Thanks,
> eric
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
prev parent reply other threads:[~2010-02-03 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 13:57 problem exporting latex fragments to html: Debian's dvipng 1.12-1 is buggy Eric S Fraga
2010-02-03 15:14 ` Carsten Dominik [this message]
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DD9B6B08-57C1-4DD3-8B3D-46DB994CF28B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).