Latest batch of fixes

Signed-off-by: Laurent Bercot <ska@appnovation.com>

10 files changed, 24 insertions, 24 deletions

diff --git a/doc/case.html b/doc/case.html
index 8ae817b..5cbca2c 100644
--- a/doc/case.html
+++ b/doc/case.html
@@ -59,16 +59,16 @@ is empty. </li>
 <ul>
  <li> <tt>-s</tt>&nbsp;: Shell matching. The <em>regex</em> words will not be
 interpreted as regular expressions, but as shell expressions to be interpreted
-via <a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/fnmatch.html">fnmatch()</a>.
+via <a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/fnmatch.html">fnmatch()</a>.
 The other options also change meanings, see the <em>Shell matching</em> section below. </li>
  <li> <tt>-S</tt>&nbsp;: Regular expression matching. This is the default. This
 section, and all of the sections below except the <em>Shell matching</em> one,
 assumes that it is the case. </li>
  <li> <tt>-e</tt>&nbsp;: Interpret the <em>regex</em> words as
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_03">basic
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap09.html#tag_09_03">basic
 regular expressions</a>. </li>
  <li> <tt>-E</tt>&nbsp;: Interpret the <em>regex</em> words as
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#tag_09_04">extended
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap09.html#tag_09_04">extended
 regular expressions</a>. This is the default. </li>
  <li> <tt>-i</tt>&nbsp;: Perform case-insensitive matches. </li>
  <li> <tt>-N</tt>&nbsp;: Make the matching expression and
@@ -129,7 +129,7 @@ to the output of the <tt>/usr/bin/env</tt> command:
  If the <tt>-s</tt> option has been given to <tt>case</tt>, then the <em>regex</em>
 words are not interpreted as regular expressions, but as shell patterns, as is
 performed by the shell's
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_09_04_05">case</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_18_09_04_05">case</a>
 conditional construct. This has the following consequences:
 </p>
 
@@ -138,10 +138,10 @@ conditional construct. This has the following consequences:
  <li> <em>prog...</em> is always executed with an unmodified environment. </li>
  <li> The options to the <tt>case</tt> command change meanings: instead of
 controlling how the <em>regex</em> regular expressions are interpreted by the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/regcomp.html">regcomp()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/regcomp.html">regcomp()</a>
 primitive, they now control how <em>value</em> is matched against the <em>regex</em> patterns
 (which are not regular expressions!) via the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/fnmatch.html">fnmatch()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/fnmatch.html">fnmatch()</a>
 primitive. Namely:
  <ul>
   <li> <tt>-e</tt>&nbsp;: Treat a backslash as an ordinary character; do not allow
diff --git a/doc/dieshdiedie.html b/doc/dieshdiedie.html
index 383bcea..a84df31 100644
--- a/doc/dieshdiedie.html
+++ b/doc/dieshdiedie.html
@@ -34,7 +34,7 @@ on the subject</a>, section 5.)
  But shells parse all the time. Worse, the <em>essence</em>
 of the shell is parsing: the parser and the runner are intimately
 interleaved and cannot be clearly separated, thanks to the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">specification</a>.
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html">specification</a>.
 The shell performs several kinds of expansions, automatic filename
 globbing, and automatic word splitting, in an unintuitive order,
 requiring users to memorize numerous arbitrary quoting rules in
@@ -143,7 +143,7 @@ can be configured to follow the slashpackage convention.
  I originally wanted a shell that could be used on an embedded system.
 Even the <tt>ash</tt> shell seemed big, so I thought of writing my
 own. Hence I had a look at the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html">sh
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html">sh
 specification</a>... and ran away screaming.
 This specification
 is <em>insane</em>. It goes against every good programming
@@ -155,7 +155,7 @@ to wannabe <tt>sh</tt> implementors.
  POSIX cannot really be blamed for that: it only normalizes existing, historical
 behaviour. One can argue whether it is a good idea to normalize atrocious
 behaviour for historical reasons, as is the case with the infamous
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/gets.html">gets</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/gets.html">gets</a>
 function, but this is the way it is.
 </p>
 
diff --git a/doc/elglob.html b/doc/elglob.html
index e9e73b1..227a4ed 100644
--- a/doc/elglob.html
+++ b/doc/elglob.html
@@ -31,7 +31,7 @@ another program.
 
 <ul>
  <li> <tt>elglob</tt> performs
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/glob.html">globbing</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/glob.html">globbing</a>
 on <em>pattern</em>. </li>
  <li> It then performs
 <a href="el_substitute.html">variable substitution</a> on
diff --git a/doc/eltest.html b/doc/eltest.html
index f2d5bf5..208b0ab 100644
--- a/doc/eltest.html
+++ b/doc/eltest.html
@@ -31,13 +31,13 @@ exit status.
 
 <p>
  <tt>eltest</tt> acts as the generic POSIX
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html">test</a> utility,
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html">test</a> utility,
 but it diverges from the specification on how it parses ambiguous arguments: see below.
 </p>
 
 <p>
  <tt>eltest</tt> supports all the standard
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html">test</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html">test</a>
 operands, plus all the extensions from
 <a href="https://man7.org/linux/man-pages/man1/test.1.html">GNU test</a>, plus a few
 extensions from the <tt>test</tt> builtin from
@@ -64,7 +64,7 @@ valid, always returns the result of the expression no matter how complex it is.
 
 <p>
  <tt>eltest</tt> <strong>is not</strong> suitable as a Single Unix
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html">test</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html">test</a>
 program, due to the way it disambiguates between arguments and operators, see below.
 However, if you never use arguments that start with a backslash, or that have the
 same name as an existing operator, then
@@ -108,7 +108,7 @@ in order to match whole strings, you must anchor <em>pattern</em> with
 <h2> Argument disambiguation </h2>
 
 <p>
- Unlike <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html">test</a>,
+ Unlike <a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html">test</a>,
 which has different fixed syntax trees depending on the number of arguments it receives and
 has undefined behaviour when called with more than 5 arguments, <tt>eltest</tt> accepts any
 number of arguments and builds its syntax trees on the fly. This means that expressions such
@@ -122,7 +122,7 @@ when it reads the second <tt>-n</tt> it exits with a syntax error.
  Doing otherwise would result in a combinatory explosion of possible syntax trees, making
 it easy for users to trigger unbounded RAM consumption, and turning a simple utility into
 a programming nightmare. This is why POSIX
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html">test</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/test.html">test</a>
 is so restricted. But we don't want the same restrictions.
 </p>
 
diff --git a/doc/execline-cd.html b/doc/execline-cd.html
index 18759d1..1727407 100644
--- a/doc/execline-cd.html
+++ b/doc/execline-cd.html
@@ -31,7 +31,7 @@ given directory, then executes a program.
 
 <p>
 <tt>execline-cd</tt> performs a
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/chdir.html">chdir()</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/chdir.html">chdir()</a>
 system call on <em>dir</em>, then execs into <em>prog...</em>.
 </p>
 
diff --git a/doc/exitcodes.html b/doc/exitcodes.html
index 3759ba7..1858b28 100644
--- a/doc/exitcodes.html
+++ b/doc/exitcodes.html
@@ -30,7 +30,7 @@ to <em>C</em>, with as much precision as possible?
 <p>
  The problem is, there's more information in a wstat (the
 structure filled in by
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/functions/waitpid.html">waitpid()</a>)
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/functions/waitpid.html">waitpid()</a>)
 than a process can report by
 simply exiting. <em>P</em> could exit with the same exit code as <em>C</em>,
 but then what should it do if C has been killed by a signal?
@@ -52,7 +52,7 @@ can report.
 
 <p>
 Shells have their own
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_08_02">convention</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/V3_chap02.html#tag_18_08_02">convention</a>
 for reporting crashes, but since any exit code greater than 127 is reported
 as is, the information given by the shell is unreliable: "child exited 129"
 and "child was killed by SIGHUP" are indistinguishable. When shells get
diff --git a/doc/getcwd.html b/doc/getcwd.html
index 62701c6..0301935 100644
--- a/doc/getcwd.html
+++ b/doc/getcwd.html
@@ -53,7 +53,7 @@ line instead of putting it into the environment. </li>
  <li> <em>var</em> must be given without a dollar! </li>
  <li> <em>var</em> must not contain <tt>=</tt>. </li>
  <li> Unlike the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pwd.html">pwd</a>
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/pwd.html">pwd</a>
 POSIX command, <tt>getcwd</tt> does not depend on the PWD environment
 variable and will exhibit a consistent behaviour no matter the environment. </li>
 </ul>
diff --git a/doc/posix-cd.html b/doc/posix-cd.html
index fc40203..baa3cdd 100644
--- a/doc/posix-cd.html
+++ b/doc/posix-cd.html
@@ -32,7 +32,7 @@ given directory, then executes a program.
 <p>
 <tt>posix-cd</tt> changes the current working directory to <em>dir</em>
 according to the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html">POSIX
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/cd.html">POSIX
 specification for a <tt>cd</tt> external utility</a>. Then, if <em>prog...</em> is
 not empty, it execs into it.
 </p>
@@ -47,7 +47,7 @@ will use <tt>posix-cd</tt>. When this configuration option has not
 been given, <tt>cd</tt> is a symbolic link to
 <a href="execline-cd.html">execline-cd</a>. </li>
  <li> <tt>posix-cd</tt> fully conforms to the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html">POSIX
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/cd.html">POSIX
 specification</a>. When <em>prog...</em> is not empty, the behaviour of a
 <tt>cd</tt> utility is not specified by POSIX, so <tt>posix-cd</tt> extends
 the spec to be actually useful and usable in an execline program with the same
diff --git a/doc/posix-umask.html b/doc/posix-umask.html
index 0d89e58..5707108 100644
--- a/doc/posix-umask.html
+++ b/doc/posix-umask.html
@@ -41,7 +41,7 @@ into it.
 
 <p>
  <tt>posix-umask</tt> interprets <em>mask</em> as specified by the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/umask.html">POSIX
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/umask.html">POSIX
 specification for a <tt>umask</tt> external utility</a>.
 </p>
 
@@ -55,7 +55,7 @@ will use <tt>posix-umask</tt>. When this configuration option has not
 been given, <tt>umask</tt> is a symbolic link to
 <a href="execline-umask.html">execline-umask</a>. </li>
  <li> <tt>posix-umask</tt> fully conforms to the
-<a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/umask.html">POSIX
+<a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/umask.html">POSIX
 specification</a>. When <em>prog...</em> is not empty, the behaviour of a
 <tt>umask</tt> utility is not specified by POSIX, so <tt>posix-umask</tt> extends
 the spec to be actually useful and usable in an execline program with the same
diff --git a/doc/wait.html b/doc/wait.html
index a66cefc..8bf06f4 100644
--- a/doc/wait.html
+++ b/doc/wait.html
@@ -74,7 +74,7 @@ Do not touch the <tt>!</tt> or <tt>?</tt> variables. This is the default. </li>
 <h2> Notes </h2>
 
 <ul>
- <li> For <a href="https://pubs.opengroup.org/onlinepubs/9699919799/utilities/wait.html">POSIX
+ <li> For <a href="https://pubs.opengroup.org/onlinepubs/9799919799/utilities/wait.html">POSIX
 compatibility</a>, <tt>wait</tt> also works when it cannot find a block.
 In that case, all the options are still supported and have the same
 effect, but the rest of the command line is interpreted as <em>pids...</em>