From: Joost Helberg <joost@snow.nl>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: :noweb no-export and syntax highlighting upon export to html
Date: Sun, 08 Nov 2015 11:39:54 +0100 [thread overview]
Message-ID: <871tc0kc5h.fsf@snow.nl> (raw)
In-Reply-To: <87k2pwv71t.fsf@gmail.com>
Dear Aaron,
I was running close to the development version, but not close
enough. It's solved now in the current version of org-mode.
At first I accepted this odd behaviour, but then I realized htmlize is
supposed to give you what you see on screen, hence this was a bug.
regards,
Joost
>>>>> "Aaron" == Aaron Ecay <aaronecay@gmail.com> writes:
> From: Aaron Ecay <aaronecay@gmail.com>
> To: Joost Helberg <joost@snow.nl>, emacs-orgmode@gnu.org
> Subject: Re: [O] :noweb no-export and syntax highlighting upon export
> Date: 2015-11-05T15:45:34+0100
> Hi Joost,
> Org’s html export relies on the syntax of the source block being valid
> in the block’s language, for the corresponding emacs major mode to
> highlight it properly. In general, I wouldn’t rely on it behaving
> properly in the presence of unexpanded noweb references. That said...
> 2015ko azaroak 5an, Joost Helberg-ek idatzi zuen:
>>
>> 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.
> Your example works fine for me on latest org master. Can you send your
> org version? (M-x org-version) What happens if you insert the code for
> t1 into an sh-mode buffer: is it highlighted as expected?
> --
> Aaron Ecay
--
Snow B.V.
next prev parent reply other threads:[~2015-11-08 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 11:38 :noweb no-export and syntax highlighting upon export to html Joost Helberg
2015-11-05 14:45 ` Aaron Ecay
2015-11-08 10:39 ` Joost Helberg [this message]
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=871tc0kc5h.fsf@snow.nl \
--to=joost@snow.nl \
--cc=aaronecay@gmail.com \
--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).