aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorUlrich Müller <ulm@gentoo.org>2019-12-04 19:05:40 +0100
committerUlrich Müller <ulm@gentoo.org>2019-12-08 12:32:06 +0100
commitb4d66635da300177037ebd65b3f33e2180007f98 (patch)
tree0dfc113adfeb004c7c9c7a463f1d87d2d687bd57 /tools-reference
parentbin/gen-eclass-html.sh: Fix text.xml output. (diff)
downloaddevmanual-b4d66635da300177037ebd65b3f33e2180007f98.tar.gz
devmanual-b4d66635da300177037ebd65b3f33e2180007f98.tar.bz2
devmanual-b4d66635da300177037ebd65b3f33e2180007f98.zip
Use <d/> for dashes throughout.
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'tools-reference')
-rw-r--r--tools-reference/bash/text.xml9
1 files changed, 5 insertions, 4 deletions
diff --git a/tools-reference/bash/text.xml b/tools-reference/bash/text.xml
index 3c4f58d..98b5675 100644
--- a/tools-reference/bash/text.xml
+++ b/tools-reference/bash/text.xml
@@ -121,7 +121,7 @@ all new code.
<p>
This is because <c>[[ ]]</c> is a bash syntax construct, whereas <c>[ ]</c> is a
-program which happens to be implemented as an internal -- as such, cleaner
+program which happens to be implemented as an internal <d/> as such, cleaner
syntax is possible with the former. For a simple illustration, consider:
</p>
@@ -604,9 +604,10 @@ These are used <e>outside</e> of the <c>[[ ]]</c> blocks. For operator precedenc
<note>
These will also sometimes work <e>inside</e> <c>[[ ]]</c> constructs, and using
-<c>!</c> before a test is fairly common. <c>[[ ! -f foo ]] &amp;&amp; bar</c> is fine. However,
-there are catches -- <c>[[ -f foo &amp;&amp; bar ]]</c> will <b>not</b> work properly, since
-commands cannot be run inside <c>[[ ]]</c> blocks.
+<c>!</c> before a test is fairly common. <c>[[ ! -f foo ]] &amp;&amp; bar</c>
+is fine. However, there are catches <d/> <c>[[ -f foo &amp;&amp; bar ]]</c>
+will <b>not</b> work properly, since commands cannot be run inside <c>[[ ]]</c>
+blocks.
</note>
<p>