From: Sharon Kimble <boudiccas@talktalk.net>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Exported source code not coloured.
Date: Sat, 15 Mar 2014 13:03:57 +0000 [thread overview]
Message-ID: <20140315130357.7f20ffb7@london> (raw)
In-Reply-To: <87pplnvf6x.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]
On Sat, 15 Mar 2014 13:06:46 +0100
Rasmus <rasmus@gmx.us> wrote:
> Sharon Kimble <boudiccas@talktalk.net> writes:
>
> > On Sat, 15 Mar 2014 10:09:29 +0000
> > Sharon Kimble <boudiccas@talktalk.net> wrote:
> >
> >> I am exporting org-mode files using org2blog, and I have this in my
> >> org-file -
> >>
> >> #+BEGIN_SRC bash
> >> ## Repos for plank
> >> # for wheezy users
> >> deb http://people.ubuntu.com/~ricotz/debian-plank wheezy main
> >> # for jessie and sid users
> >> deb http://people.ubuntu.com/~ricotz/debian-plank sid main
> >> #+END_SRC
> >>
> >> which comes out okay except it is not coloured. How can I get the
> >> exported source code to have a colour appropriate to whether its
> >> bash, or text, or python, or whatever please?
> >>
> > I forgot to say, this is Org-mode version 8.2.5h
> > (8.2.5h-32-g9639ed-elpaplus
> > @ /home/boudiccas/.emacs.d/elpa/org-plus-contrib-20140310/)
> > in emacs 24.3.1
> >
> > Am I missing a certain package that will do this for me please?
>
> Are you using async export?
>
As I don't know what 'async export' is, I can safely say "no!"
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
Debian testing, Fluxbox 1.3.5, emacs 24.3.1
Registered Linux user 561944
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-03-15 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 10:09 Exported source code not coloured Sharon Kimble
2014-03-15 11:26 ` Sharon Kimble
2014-03-15 12:06 ` Rasmus
2014-03-15 13:03 ` Sharon Kimble [this message]
2014-03-15 13:08 ` Rasmus
2014-03-15 13:24 ` 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=20140315130357.7f20ffb7@london \
--to=boudiccas@talktalk.net \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).