aboutsummaryrefslogtreecommitdiff
path: root/gsp.5
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2023-09-11 01:28:54 +0200
committerThomas Voss <mail@thomasvoss.com> 2023-09-11 01:28:54 +0200
commit1e49191f5afab7fed8a3f162c9b7e672225c2fdc (patch)
tree91c794108d6296229974b10b207024f3e65edad4 /gsp.5
parent340f5e45f3251a11830af844fd85f8934b90cf79 (diff)
Add the ‘>’ node modifier
Diffstat (limited to 'gsp.5')
-rw-r--r--gsp.532
1 files changed, 29 insertions, 3 deletions
diff --git a/gsp.5 b/gsp.5
index 87b1af8..c6678be 100644
--- a/gsp.5
+++ b/gsp.5
@@ -209,7 +209,7 @@ After
<foo><bar>Hello World</bar><baz>Hello World</baz></foo>
.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
<foo>Hello <bar>there</bar> world!</foo>
.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
<foo>Hello<bar>there</bar>world!</foo>
.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
+
+<pre><code>foo</code>
+<code>bar</code>
+<code>baz</code></pre>
+.Ed
.Sh SEE ALSO
.Xr gsp 1
.Pp