From 1e49191f5afab7fed8a3f162c9b7e672225c2fdc Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Mon, 11 Sep 2023 01:28:54 +0200 Subject: Add the ‘>’ node modifier MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- gsp.5 | 32 +++++++++++++++++++++++++++++--- 1 file changed, 29 insertions(+), 3 deletions(-) (limited to 'gsp.5') diff --git a/gsp.5 b/gsp.5 index 87b1af8..c6678be 100644 --- a/gsp.5 +++ b/gsp.5 @@ -209,7 +209,7 @@ After Hello WorldHello World .Ed .Pp -The one exception to this use is when using embedded nodes. +One exception to this use is when using embedded nodes. If your literal text contains an embedded node, then whitespace around the node is preserved: .Bd -literal -offset indent @@ -225,8 +225,8 @@ After Hello there world! .Ed .Pp -Therefore if you would like to remove the whitespace, you need to manually -compact your document: +Therefore if you would like to remove the whitespace when working with literal +text, you need to manually compact your document: .Bd -literal -offset indent Before @@ -239,6 +239,32 @@ After Hellothereworld! .Ed +.Pp +Sometimes it is also useful to have a newline between nodes, especially when +working with +.Sq code +tags nested within a +.Sq pre +tag. +To specify that you want a newline to be placed after a node, you can prefix the +node name with a greater-than symbol +.Pq Sq > : +.Bd -literal -offset indent +Before + +pre { + >code {-foo} + >code {-bar} + code {-baz} +} +.Ed +.Bd -literal -offset indent +After + +
foo
+bar
+baz
+.Ed .Sh SEE ALSO .Xr gsp 1 .Pp -- cgit v1.2.3