all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: 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: Tue, 1 Jan 2019 15:08:19 -0300	[thread overview]
Message-ID: <CAELgYhceJbQ1t=qp2mjZoBY2+Yv8QjNU7tv85n11p92wFz9sLw@mail.gmail.com> (raw)
In-Reply-To: <CAELgYhfQfoR4eidC96AdpQ_shyLYFd1wwu3wF_UpAG_4YLGTZw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 430 bytes --]

Considering the above, do you still want me to write a patch for this?

Some options:

1. Add the above as a remark in the user guide or the wiki.

2. Add a variant of the dvipng backend, say dvipng-xcolor, as explained.

3. Remove the dvipng cli color code and (maybe just deprecate or ignore)
the use-xcolor option altogether and make xcolor the default for every
backend.

4. Do nothing.

What do you think?

Regards
--
Carlos

[-- Attachment #2: Type: text/html, Size: 817 bytes --]

  reply	other threads:[~2019-01-01 18:08 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAELgYhceJbQ1t=qp2mjZoBY2+Yv8QjNU7tv85n11p92wFz9sLw@mail.gmail.com' \
    --to=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.