"M. Pger" writes:
> Actually, using -nw implies that no theme is loaded, so the face colors
> 'extracted' by htmlize are the flashy default colors of Emacs in terminal.
>
> To have the colors associated with the theme I use, I had to load the theme
> through build.el and to change my bash
Actually, using -nw implies that no theme is loaded, so the face colors
'extracted' by htmlize are the flashy default colors of Emacs in terminal.
To have the colors associated with the theme I use, I had to load the theme
through build.el and to change my bash script to:
#!/bin/sh
emacs -q
I solved the issue by creating the following bash script in my project folder:
#!/bin/sh
TERM=xterm export TERM
emacs -q -nw --load=build.el --eval="(eval-buffer)"
--eval="(save-buffers-kill-terminal)"
This avoid using --script (and thus batch) and thus allows font-lock to be
enabled when my
"M. Pger" writes:
> I tried to publish using `M-x org-publish RET RET` as you
> suggested, and
> syntax highlighting was actually implemented, thanks.
>
> Actually the problem is coming from the fact that I use `emacs -Q --script
> build.el` (as a
> bash script) to publish the project.
I tried to publish using `M-x org-publish RET RET` as you
suggested, and syntax highlighting was actually implemented, thanks.
Actually the problem is coming from the fact that I use `emacs -Q --script
build.el` (as a bash script) to publish the project. According to
"M. Pger" writes:
> Thanks for your suggestion. I added the following:
>
> #+begin_src elisp :eval no :exports code
> (setq my-var "org mailing list")
> (message "Hello, %s" my-var)
> #+end_src
>
> When exported with ~C-c C-e h o~, syntax highlighting is implemented (with
> colors). When
Thanks for your suggestion. I added the following:
#+begin_src elisp :eval no :exports code
(setq my-var "org mailing list")
(message "Hello, %s" my-var)
#+end_src
When exported with ~C-c C-e h o~, syntax highlighting is implemented (with
colors). When exported with org-publish
"M. Pger" writes:
> Thank you for your answer. Here it is:
>
> 1. Create the following directory structure (3 directories):
> ~/test/
> ├── content
> ├── html
> └── .packages
>
> 2. Create the .el script to build the website (=~/test/build.el=):
>
> #+begin_src elisp
> ;; * Set the package
Thank you for your answer. Here it is:
1. Create the following directory structure (3 directories):
~/test/
├── 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
"M. Pger" 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.
>
>
Dear All,
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
11 matches
Mail list logo
