emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joost Helberg <joost@snow.nl>
To: emacs-orgmode@gnu.org
Subject: :noweb no-export and syntax highlighting upon export to html
Date: Thu, 05 Nov 2015 12:38:43 +0100	[thread overview]
Message-ID: <87si4kk75o.fsf@snow.nl> (raw)

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

ls,

In the org-code below syntax highlighting in both code-blocks in the
emacs-buffer is fine, but the html-export only works nice in case of
using :noweb yes, the no-export option screws up syntax highlighting in
the html-output (two screenshots included).

I understood that htmlize is used for html-export and that it honours
the faces in the emacs-buffer. It seems as if htmlize doesn't do this
after encountering the '>>' token.

Can I avoid this? Are settings involved?

Org-code:

/bla/ is for re-use in scripts.
#+caption: /bla/:
#+name: bla
#+begin_src sh 
   # this sits in projects/t-stuff
#+end_src

#+caption: /t1.sh/:
#+name: t1
#+begin_src sh :tangle t1.sh :noweb no-export 
  <<bla>>
  for i in `seq 1 10`
  do
    echo $i
  done
#+end_src

#+caption: /t2.sh/:
#+name: t2
#+begin_src sh :tangle t2.sh :noweb yes 
  <<bla>>
  for i in `seq 1 10`
  do
    echo $i
  done
#+end_src


[-- Attachment #2: emacs-buffer.png --]
[-- Type: image/png, Size: 11510 bytes --]

[-- Attachment #3: org-html-export.png --]
[-- Type: image/png, Size: 17048 bytes --]

[-- Attachment #4: Type: text/plain, Size: 45 bytes --]


many regards,

Joost Helberg

-- 
Snow B.V.

             reply	other threads:[~2015-11-05 11:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05 11:38 Joost Helberg [this message]
2015-11-05 14:45 ` :noweb no-export and syntax highlighting upon export to html Aaron Ecay
2015-11-08 10:39   ` Joost Helberg
2015-11-08 17:19     ` Aaron Ecay

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=87si4kk75o.fsf@snow.nl \
    --to=joost@snow.nl \
    --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).