From 10dded485e1c2627575b2b9e21dfaabc31ee07f3 Mon Sep 17 00:00:00 2001
From: Alan Pearce
Date: Thu, 7 Jun 2018 13:55:17 +0200
Subject: Use code fences instead of template tags for syntax highlighting

---
 content/post/cedit-and-paredit.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'content/post/cedit-and-paredit.md')

diff --git a/content/post/cedit-and-paredit.md b/content/post/cedit-and-paredit.md
index a8b65a1..23fb1c4 100644
--- a/content/post/cedit-and-paredit.md
+++ b/content/post/cedit-and-paredit.md
@@ -28,12 +28,12 @@ paredit.  Turns out it provides
 that control whether a space should be inserted.  So, solving the
 formatting issue turned out to be pretty simple:
 
-{{< highlight cl >}}
+```elisp
 (defun ap/cedit-space-delimiter-p (endp delimiter)
 "Don't insert a space before delimiters in c-style modes"
 (not cedit-mode))
 (add-to-list 'paredit-space-for-delimiter-predicates #'ap/cedit-space-delimiter-p)
-{{< /highlight >}}
+```
 
 Hopefully that saves someone some time if they try to use the two
 together.
-- 
cgit 1.4.1