From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Carlos Pita <carlosjosepita@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Latex preview fg color w/tikz (known problem, fix suggested) [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.90/lisp/org/)]
Date: Thu, 06 Dec 2018 00:38:20 +0100 [thread overview]
Message-ID: <87d0qfa6j7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878t13n5qo.fsf@gmail.com> (Carlos Pita's message of "Wed, 05 Dec 2018 16:17:03 -0300")
Hello,
Carlos Pita <carlosjosepita@gmail.com> writes:
> As a more robust solution, I suggest to explicitly set the colors in the
> tex fragment for the preview instead of passing them as arguments to
> dvipng. This can be done easily:
>
> ...
> \usepackage{xcolor}
> ...
> \begin{document}
> \definecolor{bg}{rgb}{0,0,0}
> \definecolor{fg}{rgb}{1,1,1}
> \color{fg}
> \pagecolor{bg}
> ...
>
> Where fg and bg might be replaced by randomly generated string or
> whatever you see fit to prevent name clashes.
>
> Notice that the syntax for rgb color is the same than the one for dvipng
> so it shouldn't be much of a refactoring.
Would you want to provide a patch for that?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-12-05 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 19:17 Bug: Latex preview fg color w/tikz (known problem, fix suggested) [9.1.9 (release_9.1.9-65-g5e4542 @ /home/carlos/local/stow/emacs-26/share/emacs/26.1.90/lisp/org/)] Carlos Pita
2018-12-05 19:37 ` Carlos Pita
2018-12-05 23:38 ` Nicolas Goaziou [this message]
2018-12-08 4:32 ` Carlos Pita
2018-12-08 9:56 ` Nicolas Goaziou
2018-12-08 14:43 ` Eric S Fraga
2018-12-22 14:00 ` Carlos Pita
2019-01-01 18:08 ` Carlos Pita
2019-01-02 15:07 ` Nicolas Goaziou
2019-01-02 22:12 ` Carlos Pita
2019-01-03 11:35 ` Nicolas Goaziou
2019-01-03 15:38 ` Carlos Pita
2019-01-04 13:21 ` Nicolas Goaziou
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=87d0qfa6j7.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=carlosjosepita@gmail.com \
--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).