emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: silent <silent2600@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: how to control exported src color
Date: Thu, 16 Jun 2011 10:01:28 -0700	[thread overview]
Message-ID: <87ips5d5yz.fsf@gmail.com> (raw)
In-Reply-To: BANLkTinfQW7B7y1t+b-yQTx7OeD9rW+J0A@mail.gmail.com

silent <silent2600@gmail.com> writes:

> yes, I just checked my emacs, the buffer is much like the exported code,
> emacs buffer not looks that bad because it using a dark blue background,
> I changed to another color-theme, and the exported code looks much better,
> I will try to customize org-export-htmlize later.

Another option is to set the background of code segments to a dark
blue.  I often do that with the inclusion of a line like the following
in my Org-mode file.

#+style: <style type="text/css">pre{background-color: #232323; color: #E6E1DC;}</style>

Note, if you are using a color-theme, then the file defining the color
theme probably holds the html code of your background color, which could
then be copied directly as the <pre> element background.

Cheers -- Eric

> thanks!
> 2011/6/15 Jambunathan K <kjambunathan@gmail.com>:
>> silent <silent2600@gmail.com> writes:
>>> hi,
>>> I met a problem:
>>> I use #+BEGIN_SRC html #+END_SRC in org, and export to html
>>> but the source code's highlight color is not good,
>> Does your Emacs buffers look that way?
>>> could you please tell me how can I change the color ?
>> M-x customize-group RET org-export-htmlize
>> is a good starting point. But you have to do some homework.
>> Jambunathan K.
>> --

Eric Schulte

      reply	other threads:[~2011-06-16 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  6:44 how to control exported src color silent
2011-06-15 14:27 ` Jambunathan K
2011-06-16  8:21   ` silent
2011-06-16 17:01     ` Eric Schulte [this message]

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:

  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=87ips5d5yz.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=silent2600@gmail.com \


* 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


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).