Hello,
Carlos Pita writes:
> I've improved the commit message to better fit org mode conventions
> and also added a note to ORG-NEWS about the new feature. Let me know
> if there still is something I should change or feel free to amend it
> to your liking.
Applied. Thank you!
> One question fo
Hi Nicolas,
I've improved the commit message to better fit org mode conventions
and also added a note to ORG-NEWS about the new feature. Let me know
if there still is something I should change or feel free to amend it
to your liking.
One question for future patches: is it ok to add a link to the
Hello,
Carlos Pita writes:
> Here is a patch. It removes quite a few LOC.
Thank you.
> Every other previewer has :use-xcolor t. I assume it's safe to simply
> ignore :use-xcolor if it's there except that some user has configured
> a converter that for some reason requires the color command lin
Here is a patch. It removes quite a few LOC.
> I think option 3 is better. Is there any use case left for :use-xcolor?
Every other previewer has :use-xcolor t. I assume it's safe to simply
ignore :use-xcolor if it's there except that some user has configured
a converter that for some reason requi
Hello,
Carlos Pita writes:
> 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 co
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
Hi,
I found out that there is already code doing what I proposed but just
when the backend is not dvipng.
If you want to keep using dvipng you can set:
(let ((dvipng (alist-get 'dvipng org-preview-latex-process-alist)))
(plist-put dvipng :image-converter '("dvipng -D %D -T tight -o %O %f"))
On Saturday, 8 Dec 2018 at 10:56, Nicolas Goaziou wrote:
> I'm nowhere close to being a LaTeX expert. If depending on xcolor is not
> too invasive, I'd rather do it than introduce yet another customization
> option.
>
> Maybe real LaTeX experts could chime in.
Whether expert or not, I can say tha
Hello,
Carlos Pita writes:
>> Would you want to provide a patch for that?
>
> Yes, sure, just give me a few days since I'm quite busy right know.
>
> Are you ok with depending on xcolor by default or do you prefer a
> customization option?
I'm nowhere close to being a LaTeX expert. If depending
> Would you want to provide a patch for that?
Yes, sure, just give me a few days since I'm quite busy right know.
Are you ok with depending on xcolor by default or do you prefer a
customization option?
Hello,
Carlos Pita 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}
The quick and dirty option, if anyone wants it now:
(setq org-format-latex-header
(concat org-format-latex-header
"\\usepackage{xcolor}\n"
"\\definecolor{__bg__}{HTML}{1d1f21}\n"
"\\definecolor{__fg__}{HTML}{c5c8c6}\n"
"\\color{__fg__}\
12 matches
Mail list logo