From: Richard Stanton <stanton@haas.berkeley.edu>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Code blocks (partially) inherit buffer colors
Date: Fri, 1 Mar 2013 05:31:08 +0000 [thread overview]
Message-ID: <CE09F36B1F891947ACDD158E233F555A04C778@exmail10-b.haas.uc.berkeley.edu> (raw)
In-Reply-To: <871ubzn0wq.fsf@gmail.com>
Thanks, Eric.
-----Original Message-----
From: Eric Schulte [mailto:schulte.eric@gmail.com]
Sent: Thursday, February 28, 2013 9:29 PM
To: Richard Stanton
Cc: emacs-orgmode@gnu.org
Subject: Re: [O] Code blocks (partially) inherit buffer colors
Richard Stanton <stanton@haas.berkeley.edu> writes:
> When I export a code block to HTML, I've noticed that some (but not
> all) of the characters in the resulting HTML file have the same
> background color as my Emacs buffer at the time I exported. For
> example, if I export
>
> -----------
>
> #+begin_src python
> a = 5
> #+end_src
>
> ------------
>
> the code block in the resulting HTML file has a very pale background,
> except for the characters "a" and "5", both of which are displayed
> with a dark blue background that looks like it's the same as the
> background color in my Emacs buffer. This looks rather odd...
>
> I can work around this problem by changing the color-theme in my Emacs
> buffer before exporting, but is there a better solution?
>
> Thanks.
>
> Richard Stanton
See the documentation of the `org-export-htmlize-output-type' variable.
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-03-01 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-01 3:56 Code blocks (partially) inherit buffer colors Richard Stanton
2013-03-01 5:29 ` Eric Schulte
2013-03-01 5:31 ` Richard Stanton [this message]
2013-03-02 22:09 ` Richard Stanton
2013-03-04 17:48 ` Bastien
2013-03-04 18:08 ` Richard Stanton
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=CE09F36B1F891947ACDD158E233F555A04C778@exmail10-b.haas.uc.berkeley.edu \
--to=stanton@haas.berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).