Use code fences instead of template tags for syntax highlighting
1 file changed, 2 insertions(+), 2 deletions(-)
changed files
M content/post/cedit-and-paredit.md → content/post/cedit-and-paredit.md
@@ -28,12 +28,12 @@ `paredit-space-for-delimiter-predicates`, which is a list of functions 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.