From 440ea3fe6f9bfca39deae42f030ca0f36c862f98 Mon Sep 17 00:00:00 2001 From: Jonas Bernoulli Date: Wed, 12 Feb 2020 16:32:12 +0100 Subject: [PATCH] manual: Fix indentation in code blocks --- mu4e/mu4e.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index d5f3a844..99020602 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -2891,7 +2891,7 @@ Defining a new custom action comes down to writing an elisp-function to do the work. Functions that operate on messages receive a @var{msg} parameter, which corresponds to the message at point. Something like: @lisp - (defun my-action-func (msg) +(defun my-action-func (msg) "Describe my message function." ;; do stuff ) @@ -2903,7 +2903,7 @@ corresponds to the message at point, and an @var{attachment-num}, which is the number of the attachment as seen in the message view. An attachment function looks like: @lisp - (defun my-attachment-action-func (msg attachment-num) +(defun my-attachment-action-func (msg attachment-num) "Describe my attachment function." ;; do stuff )