From 6167de1a5467441d1dc2ae01ef936a6a2742b053 Mon Sep 17 00:00:00 2001
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Date: Tue, 10 Sep 2024 05:31:07 -0500
Subject: [PATCH] doc/Guidebook.mn: Use different technique.

...to get a block paragraph from the `n` package, instead of
manipulating indentation directly, which can lead to grief.
---
 doc/Guidebook.mn | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/Guidebook.mn b/doc/Guidebook.mn
index 67ad5dbb6..e800218a0 100644
--- a/doc/Guidebook.mn
+++ b/doc/Guidebook.mn
@@ -430,13 +430,15 @@ Movement modifiers:
 .lp ""
 Other conditions and modifiers exist, but there isn't enough room to
 display them with the other status fields.
+.\" Don't give the next paragraph a first-line indent.
+.nr @p \n(pi \" Save mn's paragraph indentation.
+.nr pi 0
 .pg
-.in -5n .\" outdent this paragraph
 The \f(CR#attributes\fP command (default key \f(CR\(haX\fP) will show
 all current status information in unabbreviated format.
 It also shows other information which might be included on the status
 lines if those had more room.
-.in 0 .\" reset indentation
+.nr pi \n(@p \" Restore mn's paragraph indentation.
 .hn 2
 The message line (top)
 .pg