Use code fences instead of template tags for syntax highlighting

1 files changed, 10 insertions, 10 deletions

diff --git a/content/post/opening-projects-with-projectile.md b/content/post/opening-projects-with-projectile.md
index 04f8cb6..d88d309 100644
--- a/content/post/opening-projects-with-projectile.md
+++ b/content/post/opening-projects-with-projectile.md
@@ -12,30 +12,30 @@ With this in mind, I decided to try to add support for opening projects under a
 
 I saw that projectile uses [Dash.el][] in some places, and after reading about [anaphoric macros], I decided that I'd try to use them to aid me.
 
-{{% highlight cl %}}
+```elisp
 (defun ap/subfolder-projects (dir)
   (--map (file-relative-name it dir)
          (-filter (lambda (subdir)
                     (--reduce-from (or acc (funcall it subdir)) nil
                                    projectile-project-root-files-functions))
                   (-filter #'file-directory-p (directory-files dir t "\\<")))))
-{{% /highlight %}}
+```
 
 First, this filters the non-special files under `dir`, filtering non-directories.  Then it runs the list of `projectile-project-root-files-functions` on it to determine if it looks like a projectile project.  To make the list more readable, it makes the filenames relative to the passed-in directory.  It runs like this:
                   
-{{% highlight cl %}}
+```elisp
 (ap/subfolder-projects "~/projects") =>
 ("dotfiles" "ggtags" …)
-{{% /highlight %}}
+```
 
 So, we've got ourselves a list, but now we need to be able to open the project that's there, even though the folders are relative.
 
-{{% highlight cl %}}
+```elisp
 (defun ap/open-subfolder-project (from-dir &optional arg)
   (let ((project-dir (projectile-completing-read "Open project: "
                                      (ap/subfolder-projects from-dir))))
     (projectile-switch-project-by-name (expand-file-name project-dir from-dir) arg)))
-{{% /highlight %}}
+```
 
 By wrapping the call to `ap/subfolder-projects` in another function that takes the same directory argument, we can re-use the project parent directory and expand the selected project name into an absolute path before passing it to `projectile-switch-project-by-name`.
 
@@ -43,7 +43,7 @@ We get support for multiple completion systems for free, since projectile has a
 
 Then I defined some helper functions to make it easy to open work and home projects.
 
-{{% highlight cl %}}
+```elisp
 (defvar work-project-directory "~/work")
 (defvar home-project-directory "~/projects")
 
@@ -54,7 +54,7 @@ Then I defined some helper functions to make it easy to open work and home proje
 (defun ap/open-home-project (&optional arg)
   (interactive "P")
   (ap/open-subfolder-project home-project-directory arg))
-{{% /highlight %}}
+```
 
 I could probably simplify this with a macro, but I'm not sure that there's much advantage in it.  I only have two project types right now, after all.
 
@@ -62,14 +62,14 @@ With this all set up, whenever I want to start working on a project I just type
 
 I also considered trying to add all the projects under a directory to the projectile known project list.  I didn't find it quite as easy to use, but it's available below if anyone would prefer that style.
 
-{{% highlight cl %}}
+```elisp
 (defun ap/-add-known-subfolder-projects (dir)
   (-map #'projectile-add-known-project (--map (concat (file-name-as-directory dir) it) (ap/subfolder-projects dir))))
 
 (defun ap/add-known-subfolder-projects ()
   (interactive)
   (ap/-add-known-subfolder-projects (ido-read-directory-name "Add projects under: ")))
-{{% /highlight %}}
+```
 
 [Projectile]: https://github.com/bbatsov/projectile
 [Dash.el]: https://github.com/magnars/dash.el