From: Mark Edgington <edgimar@gmail.com>
To: Mark Edgington <edgimar@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together
Date: Wed, 11 Dec 2013 09:02:36 -0500 [thread overview]
Message-ID: <CAMsBe8rLZE47RhFjC=B=yNAMwR52w8Z6D2UuXMJ61rLdxQxbRQ@mail.gmail.com> (raw)
In-Reply-To: <878uvrzsei.fsf@ucl.ac.uk>
On Wed, Dec 11, 2013 at 3:46 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> Mark Edgington <edgimar@gmail.com> writes:
>
> [...]
>
>> Is there any way that I can make it so that without a lot of "hacks" I
>> can make the previews appear as white-on-black, and the PDFs print
>> black on white? Would something need to change with how org-mode
>> handles previewing to make this possible?
[...]
> I think the key is the =org-format-latex-options= variable. I have no
> idea whether this is used by the exporter or just for previewing LaTeX
> in org.
Hi Eric,
I tried modifying org-format-latex-options (and disabling the global
'gray' TikZ setting I had previously had) like you have it, where
:foreground and :background are specified explicitly, but the result
is the same as when :foreground and :background are set to 'default'
-- the electrical components aren't visible.
It seems like what is needed is an extra key in
org-format-latex-options that allows one to add the equivalent of
#+LaTeX_HEADER: options (which only apply when (pre)viewing fragments
within emacs. Or is there some other way to make this work?
Regards,
Mark
next prev parent reply other threads:[~2013-12-11 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 15:37 TikZ (circuitikz) and org-preview-latex-fragment don't play nicely together Mark Edgington
2013-12-11 8:46 ` Eric S Fraga
2013-12-11 14:02 ` Mark Edgington [this message]
2013-12-11 15:06 ` Mark Edgington
2013-12-11 15:31 ` Nicolas Goaziou
2013-12-11 15:43 ` Mark Edgington
2013-12-11 15:55 ` 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='CAMsBe8rLZE47RhFjC=B=yNAMwR52w8Z6D2UuXMJ61rLdxQxbRQ@mail.gmail.com' \
--to=edgimar@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).