From: Sharon Kimble <boudiccas@talktalk.net>
To: Sean O'Halpin <sean.ohalpin@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Colorizing 'emacs-lisp' when it is exported?
Date: Mon, 23 Dec 2013 00:07:22 +0000 [thread overview]
Message-ID: <20131223000722.07fbd2e3@london> (raw)
In-Reply-To: <CAOXM+eVvfyB3r3J7g3qC8ApyRK7ZDWk9_y0C2E=LMugAiJSenA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1016 bytes --]
On Sun, 22 Dec 2013 23:49:04 +0000
"Sean O'Halpin" <sean.ohalpin@gmail.com> wrote:
> On Sun, Dec 22, 2013 at 4:03 PM, Sharon Kimble
> <boudiccas@talktalk.net> wrote:
> > Thanks to auntie google I've found out how to keep the formatting of
> > elisp on export to html using '#+BEGIN_SRC emacs-lisp' at the
> > beginning of the code block, and '#+END_SRC' at the end. Whilst its
> > in .emacs its nicely colorized, but how do I colorize the output
> > when its been exported please? For once, google has drawn a blank,
> > unfortunately!
> >
> > Sharon.
>
> Have you set this?
>
> (setq org-src-fontify-natively t)
No I haven't, but I have now. I'll have a further play with it tomorrow
I think. Thanks :)
Sharon.
--
A taste of linux = http://www.sharons.org.uk
efever = http://www.efever.blogspot.com/
efever = http://sharon04.livejournal.com/
my git repo = https://bitbucket.org/boudiccas/dots
Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.3.2
Registered Linux user 561944
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-23 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 16:03 Colorizing 'emacs-lisp' when it is exported? Sharon Kimble
2013-12-22 18:29 ` Jambunathan K
2013-12-22 19:00 ` Pascal J. Bourguignon
2013-12-22 23:49 ` Sean O'Halpin
2013-12-23 0:07 ` Sharon Kimble [this message]
2013-12-24 14:43 ` Sharon Kimble
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=20131223000722.07fbd2e3@london \
--to=boudiccas@talktalk.net \
--cc=emacs-orgmode@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=sean.ohalpin@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).