From 20d7909f4803ade175cd686c906a3754da51ac80 Mon Sep 17 00:00:00 2001
From: "the Phoeron\" Colin J.E. Lupton" <thephoeron@protonmail.com>
Date: Fri, 26 Aug 2022 10:27:28 -0400
Subject: [PATCH] Fix syntax highlighting and update old Bootstrap callout
 blocks to use GitBook hints plugin

---
 1-02-03-unicode.md       |  8 ++++----
 1-02-05-more-chars.md    | 10 +++++-----
 1-02-06-char-codes.md    |  7 +++----
 1-02-08-printing.md      |  6 +++---
 1-02-11-princ.md         |  7 +++----
 1-02-16-file-streams.md  |  7 +++----
 1-05-0-lookups-trees.md  |  2 +-
 1-11-0-text-adventure.md |  7 +++----
 CHANGELOG.md             | 12 ++++++++++++
 9 files changed, 37 insertions(+), 29 deletions(-)

diff --git a/1-02-03-unicode.md b/1-02-03-unicode.md
index bc4b905..70ed1ec 100644
--- a/1-02-03-unicode.md
+++ b/1-02-03-unicode.md
@@ -20,8 +20,8 @@ In SBCL, you can test specifically for Unicode support using Lisp's read-time co
 
 This code will only return a string of the cuneiform sign if you are using SBCL and you have Unicode support enabled; if you also want to see the cuneiform sign, and not a numbered Unicode box character, you have to install cuneiform fonts as well.
 
-On Arch Linux, the `ttf-akkadian` package is available in AUR.  For other platforms, you can find up-to-date links for Sumerian, Akkadian, Old Babylonian, and Neo-Assyrian fonts from the Wikipedia article for the <a href="http://en.wikipedia.org/wiki/Cuneiform_%28Unicode_block%29#Font_packages" target="_blank">Cuneiform (Unicode block)</a>.
+On Arch Linux, the `ttf-akkadian` package is available in AUR.  For other platforms, you can find up-to-date links for Sumerian, Akkadian, Old Babylonian, and Neo-Assyrian fonts from the Wikipedia article for the <a href="https://en.wikipedia.org/wiki/Cuneiform_%28Unicode_block%29#Font_packages" target="_blank">Cuneiform (Unicode block)</a>.
 
-<div class="alert alert-info" role="alert">
-  <strong>Note:</strong> Unless you plan on working with a lot of different character sets, you'll probably never notice the full Unicode support, when present.
-</div>
+{% hint style='info' %}
+Unless you plan on working with a lot of different character sets, you'll probably never notice the full Unicode support, when present.
+{% endhint %}
diff --git a/1-02-05-more-chars.md b/1-02-05-more-chars.md
index 2aa19f8..7baddfa 100644
--- a/1-02-05-more-chars.md
+++ b/1-02-05-more-chars.md
@@ -30,8 +30,8 @@ These names are not case-sensitive: you could type `#\Greek_Small_Letter_Lamda`,
 
 When you enter a character object at the REPL, it returns itself.  When you want the character's glyph, *i.e.*, what it will look like in a string, you need to put the character into a string.  This will be covered in a later exercise.
 
-<div class="alert alert-warning">
-  <strong>Note:</strong>
-  <p>You've probably noticed that the Greek letter lambda's name is "misspelled" in the example above. It's not a mistake, this is the actual character name in the Unicode standard, because the name of the letter is no longer spelled with the letter <em>beta</em> following the <em>mu</em> in modern Greek.</p>
-  <p>This is a good opportunity to remind you to type in exactly, character for character, what I have in the example code into the REPL. Did you get an error when typing the above example? Check what you typed, and make sure you typed exactly what you're supposed to.</p>
-</div>
+{% hint style='warning' %}
+You've probably noticed that the Greek letter lambda's name is "misspelled" in the example above. It's not a mistake, this is the actual character name in the Unicode standard, because the name of the letter is no longer spelled with the letter *beta* following the *mu* in modern Greek.
+
+This is a good opportunity to remind you to type in exactly, character for character, what I have in the example code into the REPL. Did you get an error when typing the above example? Check what you typed, and make sure you typed exactly what you're supposed to.
+{% endhint %}
diff --git a/1-02-06-char-codes.md b/1-02-06-char-codes.md
index 2d001ef..e94d167 100644
--- a/1-02-06-char-codes.md
+++ b/1-02-06-char-codes.md
@@ -10,10 +10,9 @@ You can get the code for a character object with the function `char-code`, and t
 (code-char #x61)
 (char-code #\a)
 ```
-
-<div class="alert alert-info">
-  See the symbol `#x61` in the example above? That's the hex-number `0x61`, which is `97` in decimal. Sometimes it's more convenient to reference integers using a different notation than decimal.  The Unicode tables are listed using hexadecimal (base-16), for instance---so you can just type the hex-number using the Sharpsign-X syntax.  There will be more discussion on numbers and notation in Chapter 1.6.
-</div>
+{% hint style='info' %}
+See the symbol `#x61` in the example above? That's the hexadecimal (base-16) number `0x61`, which is `97` in decimal (base-10). Sometimes it's more convenient to reference integers using a different notation than decimal. The Unicode tables are listed using hexadecimal, for instance---so you can just type the hex-number using the Sharpsign-X syntax. There will be more discussion on numbers and notation in Chapter 1.6.
+{% endhint %}
 
 ### What You Should See
 
diff --git a/1-02-08-printing.md b/1-02-08-printing.md
index f80e951..9501d5c 100644
--- a/1-02-08-printing.md
+++ b/1-02-08-printing.md
@@ -22,9 +22,9 @@ But lets say you want to know how an integer is printed in hexadecimal, octets,
 (write 10000 :base 2 :radix t)
 ```
 
-<div class="alert alert-info">
-  The `:radix` keyword parameter is a generalized boolean.  This means that any "non-NIL" value you pass to it will be read the same as "True", even if you don't supply `t` itself.  The only time it will be treated as "False" is when you specifically pass it `NIL`.
-</div>
+{% hint style='info' %}
+The `:radix` keyword parameter is a generalized boolean.  This means that any "non-NIL" value you pass to it will be read the same as "True", even if you don't supply `t` itself.  The only time it will be treated as "False" is when you specifically pass it `NIL`.
+{% endhint %}
 
 ### What You Should See
 
diff --git a/1-02-11-princ.md b/1-02-11-princ.md
index 5808923..c225e57 100644
--- a/1-02-11-princ.md
+++ b/1-02-11-princ.md
@@ -10,10 +10,9 @@ When you want to send a string to a stream that's meant for your users and not t
 (princ "My name is \"Colin\".")
 ```
 
-<div class="alert alert-success">
-    <strong>Tip:</strong>
-    <p>As an exception to the usual rule of "Type exactly what I type", you <em>can</em> change my name to yours whenever it comes up in a source-code example.  Just make sure it runs!</p>
-</div>
+{% hint style='tip' %}
+As an exception to the usual rule of "Type exactly what I type", you *can* change my name to yours whenever it comes up in a source-code example. Just make sure it runs!
+{% endhint %}
 
 #### What You Should See
 
diff --git a/1-02-16-file-streams.md b/1-02-16-file-streams.md
index 724f78e..d67577b 100644
--- a/1-02-16-file-streams.md
+++ b/1-02-16-file-streams.md
@@ -19,10 +19,9 @@ Like with string streams, you can create file streams manually with `open`. But
     (format t "~&;;; ~A~%" line)))
 ```
 
-<div class="alert alert-info">
-  <strong>Note:</strong>
-  <p>No animals were harmed in the making of this exercise.</p>
-</div>
+{% hint style='info' %}
+No animals were harmed in the making of this exercise.
+{% endhint %}
 
 ### What You Should See
 
diff --git a/1-05-0-lookups-trees.md b/1-05-0-lookups-trees.md
index 265dc72..6f3f7b7 100644
--- a/1-05-0-lookups-trees.md
+++ b/1-05-0-lookups-trees.md
@@ -777,7 +777,7 @@ Though of course, as always, we're not doing this replacement destructively.
 
 Now, lets do the same comparison we did earlier in the Trees section.
 
-```
+```lisp
 * (defun rec-string-assoc (key alist)
 	(cond ((null alist) nil)
           ((string= key (caar alist)) (car alist))
diff --git a/1-11-0-text-adventure.md b/1-11-0-text-adventure.md
index 871c199..f3f285b 100644
--- a/1-11-0-text-adventure.md
+++ b/1-11-0-text-adventure.md
@@ -11,10 +11,9 @@ A really important aspect of this chapter is to write a game of your very own---
 
 Once you're done working through this chapter for the second time and you get your own unique game to run, and you can play through it from beginning to end, feel free to create a repo or gist and share it in the comments below.  But remember, no cheating!  Make sure you've gone through this chapter at least twice, and successfully played through your own game, before you poke around through other people's code for ideas.
 
-<div class="alert alert-info">
-  <strong>Note:</strong>
-  <p>This chapter will guide you through writing a straightforward, hard-coded game; in other words, it will have to be recompiled every time you make a change to the source.  This doesn't necessarily represent best practices for game development.  In Parts Two and Three, alternate implementations of game engines will be presented that will load game resources on the fly from your computer's file system, so that you only have to re-compile the game when you change the program logic, and not the game content.
-</div>
+{% hint style='info' %}
+This chapter will guide you through writing a straightforward, hard-coded game; in other words, it will have to be recompiled every time you make a change to the source. This doesn't necessarily represent best practices for game development. In Parts Two and Three, alternate implementations of game engines will be presented that will load game resources on the fly from your computer's file system, so that you only have to re-compile the game when you change the program logic, and not the game content.
+{% endhint %}
 
 This chapter will contain exercises on:
 
diff --git a/CHANGELOG.md b/CHANGELOG.md
index a33c191..cdb4e1b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,17 @@
 # CHANGELOG
 
+## 2022-08-26
+
+- Fix syntax highlighting for Exercise 1.5.12, "More Tries"
+- Update callout blocks to use "hints" plugin:
+    - Exercise 1.2.3, "Unicode and Strings"
+    - Exercise 1.2.5, "More Characters"
+    - Exercise 1.2.6, "Character Codes"
+    - Exercise 1.2.8, "Printing"
+    - Exercise 1.2.11, "Printing with PRINC"
+    - Exercise 1.2.16, "File Streams"
+    - Chapter 1.11, "Extra Credit: A Simple Text Adventure"
+
 ## 2022-08-25
 
 - Exercise 1.1.8, "Configuring Your Development Environment"
-- 
GitLab