emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Roshan Shariff <roshan.shariff@gmail.com>
To: sebastien.miquel@posteo.eu
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: Can't set background color of latex fragment
Date: Sat, 10 Apr 2021 16:27:21 -0600	[thread overview]
Message-ID: <CAG8iPGy1LqWLYTqgNZA3pBUeYMzLq6UZQdgOdgSmOv0nVPS+4A@mail.gmail.com> (raw)
In-Reply-To: <ea5b72d7-a274-f80d-7161-de822515368f@posteo.eu>

I can confirm this bug with dvipng --- with the "-bg Transparent"
option, dvipng ignores the background color from the input tex file,
whereas without that option it always produces an opaque background.
There's currently no way to dynamically change command line
parameters, so I'm not sure how to solve this problem while supporting
both use cases.

On Wed, Apr 7, 2021 at 1:38 PM Sébastien Miquel
<sebastien.miquel@posteo.eu> wrote:
> To reproduce with `emacs -Q` :
>   - Open an org buffer
>   - Call ~(setq org-format-latex-options '(:foreground default
>     :background "Black" :matchers ("$")))~
>   - Call =C-c C-x C-l= (org-latex-preview) on a latex fragment such as
>     $abc$
> This bug was introduced by the commit 2f9e1569f which adds the option
> `-bg Transparent` to the arguments of `dvipng`. According to its
> manual, this option should be ignored if a background is already set,
> but it doesn't seem to be. Perhaps org should set it differently.
> --
> Sébastien Miquel

  reply	other threads:[~2021-04-10 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 19:38 Bug: Can't set background color of latex fragment Sébastien Miquel
2021-04-10 22:27 ` Roshan Shariff [this message]
2021-05-19  6:30   ` Sébastien Miquel
2021-05-20  0:30     ` Roshan Shariff
2021-05-23 21:01       ` Bug: [PATCH] " Sébastien Miquel
2021-08-29  7:22         ` Sébastien Miquel

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:

  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=CAG8iPGy1LqWLYTqgNZA3pBUeYMzLq6UZQdgOdgSmOv0nVPS+4A@mail.gmail.com \
    --to=roshan.shariff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastien.miquel@posteo.eu \


* 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).