Merge pull request #15 from hansonchar/linkfix-depth3

Fix hyperlinks of markdown pages at depth 3

Author: flokoe

docs/commands/builtin/cd.md

@@ -12,17 +12,17 @@ The `cd` builtin command is used to change the current working directory
 
 -   to the given directory (`cd DIRECTORY`)
 -   to the previous working directory (`cd -`) as saved in the
-    [OLDPWD](/syntax/shellvars#OLDPWD) shell variable
+    [OLDPWD](../../syntax/shellvars.md#OLDPWD) shell variable
 -   to the user\'s home directory as specified in the
-    [HOME](/syntax/shellvars#HOME) environment variable (when used
+    [HOME](../../syntax/shellvars.md#HOME) environment variable (when used
     without a `DIRECTORY` argument)
 
 The `cd` builtin command searches the directories listed in
-[CDPATH](/syntax/shellvars#CDPATH) for a matching directory.
+[CDPATH](../../syntax/shellvars.md#CDPATH) for a matching directory.
 
 The default behaviour is to follow symbolic links unless the `-P` option
 is given or the shell is configured to do so (see the `-P` option of
-[the set builtin command](/commands/builtin/set)).
+[the set builtin command](../../commands/builtin/set.md)).
 
 ### Options
 
@@ -36,7 +36,7 @@ is given or the shell is configured to do so (see the `-P` option of
 
 -   true if the directory was changed successfully
 -   false if a change to the home directory was requested, but
-    [HOME](/syntax/shellvars#HOME) is unset
+    [HOME](../../syntax/shellvars.md#HOME) is unset
 -   false if anything else goes wrong
 
 ## Examples
@@ -53,7 +53,7 @@ is given or the shell is configured to do so (see the `-P` option of
 
 ## See also
 
--   variable [CDPATH](/syntax/shellvars#CDPATH)
--   variable [HOME](/syntax/shellvars#HOME)
--   variable [OLDPWD](/syntax/shellvars#OLDPWD)
--   the `-P` option of [the set builtin command](/commands/builtin/set)
+-   variable [CDPATH](../../syntax/shellvars.md#CDPATH)
+-   variable [HOME](../../syntax/shellvars.md#HOME)
+-   variable [OLDPWD](../../syntax/shellvars.md#OLDPWD)
+-   the `-P` option of [the set builtin command](../../commands/builtin/set.md)

docs/commands/builtin/declare.md

@@ -176,9 +176,9 @@ for details. ksh93 namerefs are much more powerful than Bash\'s.
 
 ## See also
 
--   [arrays](/syntax/arrays)
--   [readonly](/commands/builtin/readonly)
--   [unset](/commands/builtin/unset)
+-   [arrays](../../syntax/arrays.md)
+-   [readonly](../../commands/builtin/readonly.md)
+-   [unset](../../commands/builtin/unset.md)
 -   [declaration commands](http://austingroupbugs.net/view.php?id=351)
     will change the behavior of certain builtins such as `export` in the
     next version of POSIX.

docs/commands/builtin/echo.md

@@ -8,7 +8,7 @@
 
 `echo` outputs it\'s args to stdout, separated by spaces, followed by a
 newline. The return status is always `0`. If the
-[shopt](/commands/builtin/shopt) option `xpg_echo` is set, Bash
+[shopt](../../commands/builtin/shopt.md) option `xpg_echo` is set, Bash
 dynamically determines whether echo should expand escape characters
 (listed below) by default based on the current platform. `echo` doesn\'t
 interpret `--` as the end of options, and will simply print this string
@@ -69,7 +69,7 @@ if given.
 ```
 -   **Never use options to `echo`! *Ever*!** Any time you feel tempted
     to use `echo -e`, `-n`, or any other special feature of echo, **use
-    [printf](/commands/builtin/printf) instead!** If portability is a
+    [printf](../../commands/builtin/printf.md) instead!** If portability is a
     requirement, you should consider using `printf` *exclusively* and
     just ignore that `echo` even exists. If you must use `echo -e` and
     refuse to use `printf`, it is usually acceptable to use \'\'echo
@@ -81,12 +81,12 @@ if given.
 ```
 -   `ksh93` has a `print` command, which if coding specifically for
     `ksh93` should be preferred over `echo`.
-    [printf](/commands/builtin/printf) still includes most of the
+    [printf](../../commands/builtin/printf.md) still includes most of the
     functionality of both, and should usually be the most preferred
     option.
 
 ## See also
 
--   [printf](/commands/builtin/printf)
+-   [printf](../../commands/builtin/printf.md)
 -   <http://cfajohnson.com/shell/cus-faq.html#Q0b>
 -   <http://www.in-ulm.de/~mascheck/various/echo+printf/>

docs/commands/builtin/eval.md

@@ -18,7 +18,7 @@ a child process.
 ## Examples
 
 In this example, the literal text within the
-[here-document](/syntax/redirection#here_documents) is executed as Bash
+[here-document](../../syntax/redirection.md#here_documents) is executed as Bash
 code exactly as though it were to appear within the script in place of
 the `eval` command below it.
 
@@ -135,10 +135,10 @@ first example above is the same error as the second in all non-Bash
 shells, even those with compound assignment.
 
 In the case of `eval` it isn\'t recommended to use this behavior,
-because unlike e.g. [declare](commands/builtin/declare), the initial
+because unlike e.g. [declare](../../commands/builtin/declare.md), the initial
 expansion is still subject to all expansions including
-[word-splitting](syntax/expansion/wordsplit) and [pathname
-expansion](syntax/expansion/glob).
+[word-splitting](../../syntax/expansion/wordsplit.md) and [pathname
+expansion](../../syntax/expansion/glob.md).
 
      $ ( set -x; touch 'x+=(\[[123]\]=*)' 'x+=([3]=yo)'; eval x+=(*); echo "${x[@]}" )
     + touch 'x+=(\[[123]\]=*)' 'x+=([3]=yo)'
@@ -149,14 +149,14 @@ expansion](syntax/expansion/glob).
     [[123]]=* yo
 
 Other commands known to be affected by compound assignment arguments
-include: [let](commands/builtin/let),
-[declare](commands/builtin/declare),
-[typeset](commands/builtin/typeset), [local](commands/builtin/local),
-[export](commands/builtin/export), and
-[readonly](commands/builtin/readonly). More oddities below show both
+include: [let](../../commands/builtin/let.md),
+[declare](../../commands/builtin/declare.md),
+[typeset](../../commands/builtin/typeset.md), [local](../../commands/builtin/local.md),
+[export](../../commands/builtin/export.md), and
+[readonly](../../commands/builtin/readonly.md). More oddities below show both
 similarities and differences to commands like
-[declare](commands/builtin/declare). The rules for `eval` appear
-identical to those of [let](commands/builtin/let).
+[declare](../../commands/builtin/declare.md). The rules for `eval` appear
+identical to those of [let](../../commands/builtin/let.md).
 
 ## See also
 

docs/commands/builtin/exec.md

@@ -28,7 +28,7 @@ shell without executing any program.
 -   on redirection errors it returns 1, otherwise 0
 -   on exec failures:
     -   a non-interactive shell terminates; if the [shell option
-        execfail](/internals/shell_options#execfail) is set `exec`
+        execfail](../../internals/shell_options.md#execfail) is set `exec`
         returns failure
     -   in an interactive shell, `exec` returns failure
 
@@ -82,4 +82,4 @@ exec >/var/adm/my.log 2>&1
 
 ## See also
 
--   [redirection](/syntax/redirection)
+-   [redirection](../../syntax/redirection.md)

docs/commands/builtin/exit.md

@@ -12,7 +12,7 @@ If `N` is given, the return code to the parent process is set to `N`. If
 not, the returned status the the status of the most recently executed
 command (i.e. `$?`).
 
-A [trap](/commands/builtin/trap) on `EXIT` is executed before the shell
+A [trap](../../commands/builtin/trap.md) on `EXIT` is executed before the shell
 exits, except the executed `exit` command is part of an already running
 trap.
 
@@ -42,5 +42,5 @@ executed the `exit` command, because the shell exits.
 
 ## See also
 
--   [The trap builtin command](/commands/builtin/trap)
--   [The exit status](/dict/terms/exit_status)
+-   [The trap builtin command](../../commands/builtin/trap.md)
+-   [The exit status](../../dict/terms/exit_status.md)

docs/commands/builtin/export.md

@@ -49,4 +49,4 @@ Set your default text editor (e.g. SublimeText):
 
 ## See also
 
--   [declare](/commands/builtin/declare)
+-   [declare](../../commands/builtin/declare.md)

docs/commands/builtin/let.md

@@ -7,35 +7,35 @@
 ## Description
 
 The `let` builtin command evaluates each supplied word from left to
-right as an [arithmetic expression](/syntax/arith_expr) and returns an
+right as an [arithmetic expression](../../syntax/arith_expr.md) and returns an
 exit code according to the truth value of the rightmost expression.
 
 -   0 (TRUE) when `arg` evaluated to not 0 (arithmetic \"true\")
 -   1 (FALSE) when `arg` evaluated to 0 (arithmetic \"false\")
 
 For this return code mapping, please see [this
-section](/syntax/arith_expr#arithmetic_expressions_and_return_codes).
+section](../../syntax/arith_expr.md#arithmetic_expressions_and_return_codes).
 They work in the same way as `((`.
 
 ## Examples
 
-`let` is very similar to [((](/syntax/ccmd/arithmetic_eval) - the only
+`let` is very similar to [((](../../syntax/ccmd/arithmetic_eval.md) - the only
 difference being `let` is a builtin (simple command), and `((` is a
 compound command. The arguments to `let` are therefore subject to all
 the same expansions and substitutions as any other simple command -
 requiring proper quoting and escaping - whereas the contents of `((`
-aren\'t subject to [word-splitting](/syntax/expansion/wordsplit) or
-[pathname expansion](/syntax/expansion/globs) (almost never desirable
+aren\'t subject to [word-splitting](../../syntax/expansion/wordsplit.md) or
+[pathname expansion](../../syntax/expansion/globs.md) (almost never desirable
 for arithmetic). For this reason, **the [arithmetic compound
-command](/syntax/ccmd/arithmetic_eval) should generally be preferred
+command](../../syntax/ccmd/arithmetic_eval.md) should generally be preferred
 over `let`**.
 
     $ let 'b = a' "(a += 3) + $((a = 1)), b++"
     $ echo "$a - $b - $?"
     4 - 2 - 0
 
 Is equivalent to the [arithmetic evaluation compound
-command](/syntax/ccmd/arithmetic_eval):
+command](../../syntax/ccmd/arithmetic_eval.md):
 
     $ (( b = a, (a += 3) + $((a = 1)), b++ ))
     $ echo "$a - $b - $?"
@@ -78,14 +78,14 @@ needed.
     ` Aside from differences in supported arithmetic features, this
     should be identical to the Bash/Ksh `let`.
 -   It seems to be a common misunderstanding that `let` has some legacy
-    purpose. Both `let` and [[^1]](syntax/ccmd/arithmetic_eval) were
+    purpose. Both `let` and [[^1]](../../syntax/ccmd/arithmetic_eval.md) were
     ksh88 features and almost identical in terms of portability as
     everything that inherited one also tended to get the other. Don\'t
     choose `let` over `((` expecting it to work in more places.
 -   [expr(1)](http://pubs.opengroup.org/onlinepubs/9699919799/utilities/expr.html#tag_20_42)
     is a command one is likely to come across sooner or later. While it
     is more \"standard\" than `let`, the above should always be
-    preferred. Both [arithmetic expansion](/syntax/arith_expr)s and the
+    preferred. Both [arithmetic expansion](../../syntax/arith_expr.md)s and the
     `[` test operator are specified by POSIX(r) and satisfy almost all
     of expr\'s use-cases. Unlike `let`, `expr` cannot assign directly to
     bash variables but instead returns a result on stdout. `expr` takes
@@ -96,16 +96,16 @@ needed.
     without generating any output other than a return code.
 -   For unknown reasons, `let` is one of the Bash commands with special
     parsing for arguments formatted like compound array assignments.
-    See: [eval](commands/builtin/eval#portability_considerations) for
+    See: [eval](../../commands/builtin/eval.md#portability_considerations) for
     details. There are no known practical uses for this. Parentheses are
     treated as grouping operators and compound assignment is not
     possible by arithmetic expressions.
 
 ## See also
 
--   Internal: [arithmetic expansion](/syntax/expansion/arith)
--   Internal: [arithmetic expressions](/syntax/arith_expr)
+-   Internal: [arithmetic expansion](../../syntax/expansion/arith.md)
+-   Internal: [arithmetic expressions](../../syntax/arith_expr.md)
 -   Internal: [arithmetic evaluation compound
-    command](/syntax/ccmd/arithmetic_eval)
+    command](../../syntax/ccmd/arithmetic_eval.md)
 
 [^1]: \...

docs/commands/builtin/local.md

@@ -6,7 +6,7 @@
 
 ## Description
 
-`local` is identical to [declare](/commands/builtin/declare) in every
+`local` is identical to [declare](../../commands/builtin/declare.md) in every
 way, and takes all the same options, with 3 exceptions:
 
 -   Usage outside of a function is an error. Both `declare` and `local`

docs/commands/builtin/mapfile.md

@@ -215,7 +215,7 @@ each subsequent 2 iterations. The RETURN trap is unimportant.
 
 ## See also
 
--   [arrays](/syntax/arrays)
--   [read](/commands/builtin/read) - If you don\'t know about this yet,
+-   [arrays](../../syntax/arrays.md)
+-   [read](../../commands/builtin/read.md) - If you don\'t know about this yet,
     why are you reading this page?
 -   <http://mywiki.wooledge.org/BashFAQ/001> - It\'s FAQ 1 for a reason.

docs/commands/builtin/printf.md

@@ -10,7 +10,7 @@ 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?&#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
@@ -68,8 +68,8 @@ this opens up the possibility of an easy code injection vulnerability.
 \...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
 signal the end of options. The exact same issue also applies to
-[read](commands/builtin/read), and a similar one to
-[mapfile](commands/builtin/mapfile), though performing expansions into
+[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\>
 
 ### Arguments
@@ -93,9 +93,9 @@ interpreted. If fewer format specifiers than arguments are present, then
 number-formats are set to zero, while string-formats are set to null
 (empty).
 
-Take care to avoid [word splitting](/syntax/expansion/wordsplit), as
+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).
+different and unexpected results. See [this article](../../syntax/words.md).
 
 \<note warning\> [**Again, attention:**]{.underline} When a numerical
 format expects a number, the internal `printf`-command will use the
@@ -234,7 +234,7 @@ associated with a `%b` format:
     (POSIX specifies up to three).
 
 These are also respects in which `%b` differs from the escapes used by
-[\$\'\...\'](syntax/quoting#ansi_c_like_strings) style quoting.
+[\$\'\...\'](../../syntax/quoting.md#ansi_c_like_strings) style quoting.
 
 ## Examples
 
@@ -447,7 +447,7 @@ fmt++;
 
 -   The optional Bash loadable `print` may be useful for ksh
     compatibility and to overcome some of
-    [echo](commands/builtin/echo)\'s portability pitfalls. Bash, ksh93,
+    [echo](../../commands/builtin/echo.md)\'s portability pitfalls. Bash, ksh93,
     and zsh\'s `print` have an `-f` option which takes a `printf` format
     string and applies it to the remaining arguments. Bash lists the
     synopsis as:
@@ -461,7 +461,7 @@ fmt++;
 ```
 -   Assigning to variables: The `printf -v` way is slightly different to
     the way using command-substitution. [Command
-    substitution](/syntax/expansion/cmdsubst) removes trailing newlines
+    substitution](../../syntax/expansion/cmdsubst.md) removes trailing newlines
     before substituting the text, `printf -v` preserves all output.
 
 ## See also
@@ -471,6 +471,6 @@ fmt++;
     and [printf()
     function](http://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html)
 -   [Code snip: Print a horizontal
-    line](/snipplets/print_horizontal_line) uses some `printf` examples
+    line](../../snipplets/print_horizontal_line.md) uses some `printf` examples
 -   [Greg\'s BashFAQ 18: How can I use numbers with leading zeros in a
     loop, e.g., 01, 02?](BashFAQ>018)

docs/commands/builtin/read.md

@@ -16,13 +16,13 @@ Since Bash 4.3-alpha, `read` skips any `NUL` (ASCII code 0) characters
 in input.
 
 If `<NAME...>` is given, the line is word-split using
-[IFS](/syntax/shellvars#IFS) variable, and every word is assigned to one
+[IFS](../../syntax/shellvars.md#IFS) variable, and every word is assigned to one
 `<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
 read (without performing word-splitting!) is assigned to the shell
-variable [REPLY](/syntax/shellvars#REPLY). Then, `REPLY` really contains
+variable [REPLY](../../syntax/shellvars.md#REPLY). Then, `REPLY` really contains
 the line as it was read, without stripping pre- and postfix spaces and
 other things!
 
@@ -33,7 +33,7 @@ other things!
 \</WRAP\>
 
 If a timeout is given, or if the shell variable
-[TMOUT](/syntax/shellvars#TMOUT) is set, it is counted from initially
+[TMOUT](../../syntax/shellvars.md#TMOUT) is set, it is counted from initially
 waiting for input until the completion of input (i.e. until the complete
 line is read). That means the timeout can occur during input, too.
 
@@ -64,7 +64,7 @@ Of course it\'s valid to set individual array elements without using
 \<WRAP center round important 90%\>
 
 Reading into array elements using the syntax above **may cause [pathname
-expansion](/syntax/expansion/globs) to occur**.
+expansion](../../syntax/expansion/globs.md) to occur**.
 
 Example: You are in a directory with a file named `x1`, and you want to
 read into an array `x`, index `1` with
@@ -172,7 +172,7 @@ Take care that you cannot use a pipe:
 Why? because the commands of the pipe run in subshells that cannot
 modify the parent shell. As a result, the variables `col1`, `col2` and
 `col3` of the parent shell are not modified (see article:
-[processtree](/scripting/processtree)).
+[processtree](../../scripting/processtree.md)).
 
 If the variable has more fields than there are variables, the last
 variable get the remaining of the line:
@@ -184,7 +184,7 @@ variable get the remaining of the line:
 
 By default reads separates the line in fields using spaces or tabs. You
 can modify this using the *special variable*
-[IFS](/syntax/shellvars#IFS), the Internal Field Separator.
+[IFS](../../syntax/shellvars.md#IFS), the Internal Field Separator.
 
     IFS=":" read -r col1 col2 <<< "hello:world"
     printf "col1: %s col2: %s\n" "$col1" "$col2"
@@ -264,6 +264,6 @@ date/time string are recognized correctly.
 
 ## See also
 
--   Internal: [The printf builtin command](/commands/builtin/printf)
+-   Internal: [The printf builtin command](../../commands/builtin/printf.md)
 
 [^1]: fixed in 4.2-rc1