emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "M. Pger" <mpger@protonmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: no syntax highlighting for code blocks with org-publish
Date: Mon, 18 Jul 2022 08:57:38 +0000	[thread overview]
Message-ID: <xhmnViLdAGK813ymofCfMMjzDtOpioA5s18k7xMxQ2VASRyCo1Emlu-4-Sa_5e9OPsU0JrLlre1pL4QBihOmrMusAURzwb23jqqZwWHXqGs=@protonmail.com> (raw)
In-Reply-To: <87zgh7i9vk.fsf@localhost>

Thank you for your answer. Here it is:

1. Create the following directory structure (3 directories):
├── content
├── html
└── .packages

2. Create the .el script to build the website (=~/test/build.el=):

#+begin_src elisp
  ;; * Set the package installation directory (in order not to overwrite the standard ~/emacs.d)
  (require 'package)
  (setq package-user-dir (expand-file-name "./.packages"))
  (setq package-archives '(("melpa" . "https://melpa.org/packages/")))
  (add-to-list 'package-archives '("elpa" . "https://elpa.gnu.org/packages/"))

  ;; * Initialize the package system
  (unless package-archive-contents

  ;; * Install dependencies
  ;; ** since org is builtin, by default Emacs does not try to install the latest version from Elpa (9.5.4)
  ;; the following solves the issue:
  (defun mpger-ignore-builtin (pkg)
    (assq-delete-all pkg package--builtins)
    (assq-delete-all pkg package--builtin-versions))
  (mpger-ignore-builtin 'org)
  ;; ** install packages:
  (package-install 'org)
  (package-install 'htmlize)

  ;; * Load the publishing system:
  (require 'org)
  (require 'htmlize)
  (require 'ox-publish)

  ;; * Define the project
  (setq org-publish-project-alist
	 (list "pages"
	       :recursive t
	       :htmlized-source t
	       :base-directory "./content/"
	       :base-extension "org"
	       :publishing-directory "./html/"
	       :publishing-function 'org-html-publish-to-html
	       :with-creator t
	       :with-toc t
	       :section-numbers nil
	       :time-stamp-file nil)

  ;; * Generate the site output
  (org-publish-all t)

  (message "Done!")

3. In =~/test/content/=, create a simple test.org file to be published as html (=~/test/content/test.org=):

* Here's some text

Lorem ipsum.

* Here's some code

#+begin_src R :results output :exports both
  df <- mtcars ## a comment

4. Run =~/test/build.el= (e.g. with ~emacs -Q --script ~/test/build.el~) and compare with the output from ~C-c C-e h o~. The latter has syntax highlighting, the former has not.



------- Original Message -------
On Monday, July 18th, 2022 at 1:42 AM, Ihor Radchenko <yantar92@gmail.com> wrote:

> "M. Pger" mpger@protonmail.com writes:
> > While syntax highlighting for code blocks is correctly implemented when I export a Org document with M-x org-html-export-to-html, it does not work when the same document is exported as part of an org-publish project defined using org-publish-project-alist.
> >
> > Org-version: 9.5.4 (also tried with 9.5.2)
> > Htmlize-version: 1.57
> >
> > Note that including :htmlized-source t does not solve the problem.
> >
> > Any idea of what's happening?
> May you provide an example reproducer?
> Best,
> Ihor

  reply	other threads:[~2022-07-18  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 17:24 no syntax highlighting for code blocks with org-publish M. Pger
2022-07-17 23:42 ` Ihor Radchenko
2022-07-18  8:57   ` M. Pger [this message]
2022-07-18 21:50     ` Tim Cross
2022-07-18 22:55       ` M. Pger
2022-07-19  7:51         ` Tim Cross
2022-07-19 15:34           ` M. Pger
2022-07-19 22:33             ` Tim Cross
2022-07-19 23:14               ` M. Pger
2022-07-20  5:22                 ` M. Pger
2022-07-21 11:38                   ` Ihor Radchenko

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='xhmnViLdAGK813ymofCfMMjzDtOpioA5s18k7xMxQ2VASRyCo1Emlu-4-Sa_5e9OPsU0JrLlre1pL4QBihOmrMusAURzwb23jqqZwWHXqGs=@protonmail.com' \
    --to=mpger@protonmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).