typst PDF: re-add missing images (editors)

for #509

Author: vindarel

dandelion.png assets/dandelion.pngdandelion.png renamed to assets/dandelion.png

@@ -19,6 +19,12 @@ to display GUI windows with Win32, Tk, IUP, ftw and Opengl.
 <img src="assets/plain-cl-slime-interaction.png"
      style="max-width: 800px" alt="Emacs and SLIME."/>
 
+<!-- pdf-include-start
+![](assets/plain-cl-slime-interaction.png)
+   pdf-include-end -->
+
+<!-- todo: PDF generation: lacks IMG images -->
+
 
 ### Using Emacs as an IDE
 
@@ -37,6 +43,10 @@ for Vim.
 <img src="assets/slimv.jpg"
      style="width: 800px" alt="The Slimv plugin with an open REPL"/>
 
+<!-- pdf-include-start
+![](assets/slimv.jpg)
+   pdf-include-end -->
+
 [cl-neovim](https://github.com/adolenc/cl-neovim/) makes it possible to write
 Neovim plugins in Common Lisp.
 
@@ -73,6 +83,10 @@ It is based on the Swank backend, like Slime for Emacs.
 <img src="assets/atom-slime.png"
      style="width: 800px" alt="The SLIMA extension for Atom with an open Lisp REPL"/>
 
+<!-- pdf-include-start
+![](assets/atom-slime.png)
+   pdf-include-end -->
+
 ## VSCode
 
 [Alive](https://marketplace.visualstudio.com/items?itemName=rheller.alive) makes
@@ -101,6 +115,10 @@ supports:
 
 <img src="assets/commonlisp-vscode-alive.png" style="width: 800px" alt="The Alive VSCode plugin showing the interactive debugger."/>
 
+<!-- pdf-include-start
+![](assets/commonlisp-vscode-alive.png)
+   pdf-include-end -->
+
 [commonlisp-vscode
 extension](https://marketplace.visualstudio.com/items?itemName=ailisp.commonlisp-vscode)
 works via the [cl-lsp](https://github.com/ailisp/cl-lsp) language server and
@@ -117,6 +135,12 @@ supports:
 
 <img src="assets/commonlisp-vscode.png" style="width: 800px" alt="The VSCode extension with a Lisp REPL, code completion and a mini-map."/>
 
+
+<!-- pdf-include-start
+![](assets/commonlisp-vscode.png)
+   pdf-include-end -->
+
+
 ### Using VSCode with Alive
 
 See [Using VSCode with Alive](vscode-alive.html).
@@ -146,6 +170,10 @@ At the time of writing, for its version 0.4, it supports:
 
 <img src="assets/jetbrains-slt.png" style="width: 800px" alt="SLT, a good Common Lisp plugin for JetBrains IDEs."/>
 
+<!-- pdf-include-start
+![](assets/jetbrains-slt.png)
+   pdf-include-end -->
+
 
 ## Eclipse
 
@@ -156,7 +184,11 @@ Available for Windows, Mac and Linux, built-in SBCL and CLISP support
 and possibility to connect other environments, interactive debugger
 with restarts, macro-expansion, parenthesis matching,…
 
-<img src="dandelion.png" style="width: 800px" alt="Dandelion, a simple Common Lisp plugin for Eclipse"/>
+<img src="assets/dandelion.png" style="width: 800px" alt="Dandelion, a simple Common Lisp plugin for Eclipse"/>
+
+<!-- pdf-include-start
+![](assets/dandelion.png)
+   pdf-include-end -->
 
 ## Lem
 
@@ -169,6 +201,10 @@ Python, Go, Rust, JS, Nim, Scheme, HTML, CSS, plus a directory mode, a **vim lay
 <img src="assets/lem-sdl2.png"
      style="width: 800px" alt="Lem running in a SDL2 GUI."/>
 
+<!-- pdf-include-start
+![](assets/lem-sdl2.png)
+   pdf-include-end -->
+
 It can be started as a REPL right away in the terminal. Run it with:
 
     lem --eval "(lem-lisp-mode:start-lisp-repl t)"
@@ -184,6 +220,11 @@ There is more:
 
 <img src="assets/lem1.png" style="width: 800px" title="Lem's REPL" alt="Lem running in the terminal with the Lisp REPL full screen, showing a completion window."/>
 
+<!-- pdf-include-start
+![](assets/lem1.png)
+   pdf-include-end -->
+
+
 ## Sublime Text
 
 [Sublime Text](http://www.sublimetext.com/3) has now good support for
@@ -201,6 +242,11 @@ inspection.
 <img src="assets/editor-sublime.png"
      style="width: 800px" alt="A Lisp REPL in Sublime Text"/>
 
+<!-- pdf-include-start
+![](assets/editor-sublime.png)
+   pdf-include-end -->
+
+
 ## LispWorks (proprietary)
 
 [LispWorks](http://www.lispworks.com/) is a Common Lisp implementation that
@@ -212,6 +258,10 @@ You can [read our LispWorks review here](lispworks.html).
 
 <img src="assets/lispworks/two-sided-view.png" style="width: 800px" title="The LispWorks IDE" alt="The LispWorks listener and the editor in the Mate desktop environment"/>
 
+<!-- pdf-include-start
+![](assets/lispworks/two-sided-view.png)
+   pdf-include-end -->
+
 
 ## Geany (experimental)
 
@@ -222,6 +272,10 @@ highlighting of errors and warnings, a REPL, and a project skeleton creator.
 
 <img src="assets/geany.png" style="width: 800px" alt="The Geany Lisp plugin showing compilation warnings"/>
 
+<!-- pdf-include-start
+![](assets/geany.png)
+   pdf-include-end -->
+
 
 ## Notebooks
 
@@ -233,6 +287,10 @@ You can [see a live Jupyter notebook written in Lisp here](https://nbviewer.jupy
 <img src="assets/jupyterpreview.png"
      style="width: 800px" alt="A Jupyter notebook running a Common Lisp kernel, exploring the Lorentz system of differential equations, showing a colorful 3D plot with interactive controls (note: the code in the screenshot is actually not Lisp!)"/>
 
+<!-- pdf-include-start
+![](assets/jupyterpreview.png)
+   pdf-include-end -->
+
 There is also [Darkmatter](https://github.com/tamamu/darkmatter), a notebook-style
 Common Lisp environment, built in Common Lisp.
 
@@ -248,6 +306,10 @@ You might also like [sbcli](https://github.com/hellerve/sbcli), an even simpler
 <img src="assets/cl-repl.png"
      style="width: 500px" alt="cl-repl 0.4.1 runnning in the terminal, built with Roswell, featuring multi-line prompts and syntax highlighting."/>
 
+<!-- pdf-include-start
+![](assets/cl-repl.png)
+   pdf-include-end -->
+
 
 ## Others
 

editor-support.md

@@ -0,0 +1,3 @@
+
+s/<!-- pdf-include-start//g
+s/pdf-include-end -->//g

include-pdf-images.sed

@@ -100,6 +100,10 @@
   and the typst binary on the path."
   (format t "~&Generating the pdf with pandoc >= 3.8 and Typst...~&")
 
+  ;; Include images for the PDF.
+  ;; The issue: our images in HTLM <img> tags are not brought along in the .typ then PDF.
+  (uiop:run-program (format nil "~a -i -f include-pdf-images.sed ~a" *sed-command* *full-markdown*))
+
   ;; Transform our md file to .typ:
   (uiop:run-program (format nil "pandoc -o full.typ ~a" *full-markdown*)
                     :output t