format(docs): replace escaped special characters

Author: coronary

docs/commands/builtin/declare.md

@@ -138,7 +138,7 @@ RHS.
     sum total a b c
     printf 'Final value of "total" is: %d\n' "$total"
 
-\<div hide\> function sum {
+<div hide> function sum {
 
       typeset -n _result=$1
       shift
@@ -153,7 +153,7 @@ RHS.
 }
 
 a=(1 2 3); b=(6 5 4); c=(2 4 6) sum total a b c printf \'Final value of
-\"total\" is: %d\\n\' \"\$total\" \</div\>
+\"total\" is: %d\\n\' \"\$total\" </div>
 
 `typeset -n` is currently implemented in ksh93, mksh, and Bash 4.3. Bash
 and mksh's implementations are quite similar, but much different from

docs/commands/builtin/eval.md

@@ -109,7 +109,7 @@ controlled carefully by the caller is a good way to use it.
     ~~ksh93~~ and zsh don't do this properly
     ([fixed](http://article.gmane.org/gmane.comp.programming.tools.ast.devel/686)
     in ksh 93v- 2012-10-24 alpha). Earlier versions of zsh work (with
-    `setopt POSIX_BUILTINS` \-- looks like a regression). This works
+    `setopt POSIX_BUILTINS` -- looks like a regression). This works
     correctly in Bash POSIX mode, Dash, and mksh.
 
 ```{=html}
@@ -161,14 +161,14 @@ identical to those of [let](../../commands/builtin/let.md).
 ## See also
 
 -   [BashFAQ 48 - eval and security
-    issues](http://mywiki.wooledge.org/BashFAQ/048) \-- **IMPORTANT**
+    issues](http://mywiki.wooledge.org/BashFAQ/048) -- **IMPORTANT**
 -   [Another eval
     article](http://fvue.nl/wiki/Bash:_Why_use_eval_with_variable_expansion%3F)
 -   [Indirection via
     eval](http://mywiki.wooledge.org/BashFAQ/006#Assigning_indirect.2BAC8-reference_variables)
 -   [More indirection via
     eval](http://fvue.nl/wiki/Bash:_Passing_variables_by_reference)
--   [Martin Väth's \"push\"](https://github.com/vaeth/push) \--
+-   [Martin Väth's \"push\"](https://github.com/vaeth/push) --
     `printf %q` work-alike for POSIX.
 -   [The \"magic alias\"
     hack](http://www.chiark.greenend.org.uk/~sgtatham/aliases.html)

docs/commands/builtin/let.md

@@ -41,12 +41,12 @@ command](../../syntax/ccmd/arithmetic_eval.md):
     $ echo "$a - $b - $?"
     4 - 2 - 0
 
-\<WRAP info\> Remember that inside arithmetic evaluation contexts, all
+<WRAP info> Remember that inside arithmetic evaluation contexts, all
 other expansions are processed as usual (from left-to-right), and the
 resulting text is evaluated as an arithmetic expression. Arithmetic
 already has a way to control precedence using parentheses, so it's very
 rare to need to nest arithmetic expansions within one another. It's
-used above only to illustrate how this precedence works. \</WRAP\>
+used above only to illustrate how this precedence works. </WRAP>
 
 Unlike `((`, being a simple command `let` has its own environment. In
 Bash, built-ins that can set variables process any arithmetic under

docs/commands/builtin/mapfile.md

@@ -121,7 +121,7 @@ illustrates the callback behavior:
 
 Since redirects are syntactically allowed anywhere in a command, we put
 it before the printf to stay out of the way of additional arguments.
-Rather than opening \"outfile\<n\>\" for appending on each call by
+Rather than opening \"outfile<n>\" for appending on each call by
 calculating the filename, open an FD for each first and calculate which
 FD to send output to by measuring the size of x mod 2. The zero-width
 format specification is used to absorb the index number argument.

docs/commands/builtin/printf.md

@@ -1,16 +1,16 @@
 # The printf command
 
-\<div center round todo box 70%\> FIXME Stranger, this is a very big
+<div center round todo box 70%> FIXME Stranger, this is a very big
 topic that needs experience - please fill in missing information, extend
-the descriptions, and correct the details if you can! \</div\> \<div
-center round tip 70%\> [**Attention:**]{.underline} This is about the
+the descriptions, and correct the details if you can! </div> <div
+center round tip 70%> [**Attention:**]{.underline} This is about the
 Bash-builtin command `printf` - however, the description should be
 nearly identical for an external command that follows POSIX(r).
 
 [GNU Awk](http://www.gnu.org/software/gawk/manual/gawk.html#Printf)
 expects a comma after the format string and between each of the
 arguments of a **printf** command. For examples, see: [code
-snippet](../../printf?&.md#using_printf_inside_of_awk). \</div\>
+snippet](../../printf?&.md#using_printf_inside_of_awk). </div>
 
 Unlike other documentations, I don't want to redirect you to the manual
 page for the `printf()` C function family. However, if you\'re more
@@ -57,7 +57,7 @@ argument!).
 The `-v` Option can't assign directly to array indexes in Bash versions
 older than Bash 4.1.
 
-\<note warning\> In versions newer than 4.1, one must be careful when
+<note warning> In versions newer than 4.1, one must be careful when
 performing expansions into the first non-option argument of printf as
 this opens up the possibility of an easy code injection vulnerability.
 
@@ -66,11 +66,11 @@ this opens up the possibility of an easy code injection vulnerability.
     declare -a x='([0]="hi")'
 
 \...where the echo can of course be replaced with any arbitrary command.
-If you must, either specify a hard-coded format string or use \-- to
+If you must, either specify a hard-coded format string or use -- to
 signal the end of options. The exact same issue also applies to
 [read](../../commands/builtin/read.md), and a similar one to
 [mapfile](../../commands/builtin/mapfile.md), though performing expansions into
-their arguments is less common. \</note\>
+their arguments is less common. </note>
 
 ### Arguments
 
@@ -97,15 +97,15 @@ Take care to avoid [word splitting](../../syntax/expansion/wordsplit.md), as
 accidentally passing the wrong number of arguments can produce wildly
 different and unexpected results. See [this article](../../syntax/words.md).
 
-\<note warning\> [**Again, attention:**]{.underline} When a numerical
+<note warning> [**Again, attention:**]{.underline} When a numerical
 format expects a number, the internal `printf`-command will use the
 common Bash arithmetic rules regarding the base. A command like the
 following example **will** throw an error, since `08` is not a valid
 octal number (`00` to `07`!):
 
     printf '%d\n' 08
 
-\</note\>
+</note>
 
 ### Format strings
 
@@ -216,8 +216,8 @@ argument corresponding to a `%b` format.
   `\v`             Prints a vertical tabulator
   `\"`             Prints a `'`
   `\?`             Prints a `?`
-  `\<NNN>`         Interprets `<NNN>` as **octal** number and prints the corresponding character from the character set
-  `\0<NNN>`        same as `\<NNN>`
+  `<NNN>`         Interprets `<NNN>` as **octal** number and prints the corresponding character from the character set
+  `\0<NNN>`        same as `<NNN>`
   `\x<NNN>`        Interprets `<NNN>` as **hexadecimal** number and prints the corresponding character from the character set (**3 digits**)
   `\u<NNNN>`       same as `\x<NNN>`, but **4 digits**
   `\U<NNNNNNNN>`   same as `\x<NNN>`, but **8 digits**
@@ -412,7 +412,7 @@ fmt++;
     system's `/usr/bin/printf` or equivalent. The mksh maintainer
     recommends using `print`. The development version (post- R40f) adds
     a new parameter expansion in the form of `${name@Q}` which fills the
-    role of `printf %q` \-- expanding in a shell-escaped format.
+    role of `printf %q` -- expanding in a shell-escaped format.
 
 ```{=html}
 <!-- -->

docs/commands/builtin/read.md

@@ -20,7 +20,7 @@ If `<NAME...>` is given, the line is word-split using
 `<NAME>`. The remaining words are all assigned to the last `<NAME>` if
 more words than variable names are present.
 
-\<WRAP center round info 90%\> If no `<NAME>` is given, the whole line
+<WRAP center round info 90%> If no `<NAME>` is given, the whole line
 read (without performing word-splitting!) is assigned to the shell
 variable [REPLY](../../syntax/shellvars.md#REPLY). Then, `REPLY` really contains
 the line as it was read, without stripping pre- and postfix spaces and
@@ -30,7 +30,7 @@ other things!
       printf '"%s"\n' "$REPLY"
     done <<<"  a line with prefix and postfix space  "
 
-\</WRAP\>
+</WRAP>
 
 If a timeout is given, or if the shell variable
 [TMOUT](../../syntax/shellvars.md#TMOUT) is set, it is counted from initially
@@ -61,7 +61,7 @@ Of course it's valid to set individual array elements without using
 
     read MYARRAY[5]
 
-\<WRAP center round important 90%\>
+<WRAP center round important 90%>
 
 Reading into array elements using the syntax above **may cause [pathname
 expansion](../../syntax/expansion/globs.md) to occur**.
@@ -81,7 +81,7 @@ array name and index:
 
     read 'x[1]'
 
-\</WRAP\>
+</WRAP>
 
 ### Return status
 
@@ -90,7 +90,7 @@ array name and index:
   0        no error
   0        error when assigning to a read-only variable [^1]
   2        invalid option
-  \>128    timeout (see `-t`)
+  >128    timeout (see `-t`)
   !=0      invalid filedescriptor supplied to `-u`
   !=0      end-of-file reached
 

docs/commands/builtin/set.md

@@ -41,7 +41,7 @@ set flags (true for most commands on UNIX(r)).
   `-v`   `verbose`                                                  Print shell input lines as they are read - useful for debugging.
   `-x`   `xtrace`                                                   Print commands just before execution - with all expansions and substitutions done, and words marked - useful for debugging.
   `-B`   `braceexpand`                                              The shell performs [brace expansion](../../syntax/expansion/brace.md) This is on by default.
-  `-C`   \<BOOKMARK:tag_noclobber\>`noclobber`                      Don't overwrite files on redirection operations. You can override that by specifying the `>|` redirection operator when needed. See [redirection](../../syntax/redirection.md)
+  `-C`   <BOOKMARK:tag_noclobber>`noclobber`                      Don't overwrite files on redirection operations. You can override that by specifying the `>|` redirection operator when needed. See [redirection](../../syntax/redirection.md)
   `-E`   `errtrace`                                                 `ERR`-traps are inherited by by shell functions, command substitutions, and commands executed in a subshell environment.
   `-H`   `histexpand`                                               Enable `!`-style history expansion. Defaults to `on` for interactive shells.
   `-P`   `physical`                                                 Don't follow symlinks when changing directories - use the physical filesystem structure.

docs/commands/builtin/shift.md

@@ -63,26 +63,26 @@ There are no options.
     dash: 1: shift: can't shift that many
     ` In most shells, you can work around this problem using the
     [command](../../commands/builtin/command.md) builtin to suppress fatal
-    errors caused by *special builtins*. \<code\> \$ dash -c \'f() { if
-    command shift 2\>/dev/null; then echo \"\$1\"; else echo \"no
+    errors caused by *special builtins*. <code> \$ dash -c \'f() { if
+    command shift 2>/dev/null; then echo \"\$1\"; else echo \"no
     args\"; fi; }; f\'
 
-no args \</code\> While, POSIX requires this behavior, it isn't very
+no args </code> While, POSIX requires this behavior, it isn't very
 obvious and some shells don't do it correctly. To work around this, you
 can use something like:
 
-\<code\> \$ mksh -c \'f() { if ! \${1+false} && shift; then echo
-\"\$1\"; else echo \"no args\"; fi; }; f\' no args \</code\> ~~The mksh
+<code> \$ mksh -c \'f() { if ! \${1+false} && shift; then echo
+\"\$1\"; else echo \"no args\"; fi; }; f\' no args </code> ~~The mksh
 maintainer refuses to change either the `shift` or `command` builtins.~~
 [Fixed](https://github.com/MirBSD/mksh/commit/996e05548ab82f7ef2dea61f109cc7b6d13837fa).
 (Thanks!)
 
 -   Perhaps almost as bad as the above, busybox sh's `shift` always
     returns success, even when attempting to shift beyond the final
-    argument. \<code\> \$ bb -c \'f() { if shift; then echo \"\$1\";
+    argument. <code> \$ bb -c \'f() { if shift; then echo \"\$1\";
     else echo \"no args\"; fi; }; f\'
 
-(no output) \</code\> The above mksh workaround will work in this case
+(no output) </code> The above mksh workaround will work in this case
 too.
 
 ## See also