From c0966f6327d1868647d015629afd53b59bcb8dc0 Mon Sep 17 00:00:00 2001
From: Laurent Bercot
Date: Sun, 4 Oct 2020 17:07:24 +0000
Subject: doc: fix URLs
---
doc/dieshdiedie.html | 14 +++++++-------
doc/el_substitute.html | 2 +-
doc/el_transform.html | 2 +-
doc/elglob.html | 2 +-
doc/execline-cd.html | 2 +-
doc/exitcodes.html | 4 ++--
doc/fdreserve.html | 2 +-
doc/getcwd.html | 2 +-
doc/grammar.html | 4 ++--
doc/index.html | 4 ++--
doc/multisubstitute.html | 2 +-
doc/runblock.html | 2 +-
12 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/doc/dieshdiedie.html b/doc/dieshdiedie.html
index 9dd2313..75e660f 100644
--- a/doc/dieshdiedie.html
+++ b/doc/dieshdiedie.html
@@ -26,7 +26,7 @@
One of the most frequent sources of security problems in programs
is parsing. Parsing is a complex operation, and it is easy to
make mistakes while designing and implementing a parser. (See
-what Dan Bernstein says
+what Dan Bernstein says
on the subject, section 5.)
@@ -34,12 +34,12 @@ on the subject, section 5.)
But shells parse all the time. Worse, the essence
of the shell is parsing: the parser and the runner are intimately
interleaved and cannot be clearly separated, thanks to the
-specification.
+specification.
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
order to achieve what they want. Pages
-abound
+abound
where common mistakes are listed, more often than not leading to
security holes. Did you know that "$@" is a special case
of double quoting, because it will split the arguments into
@@ -80,7 +80,7 @@ cannot be used safely with the normalized options, because most shells
come with a builtin test that does not respect the
specification to the letter. And let's not get started about echo,
which has its own set of problems. Rich Felker has
-a page listing tricks
+a page listing tricks
to use to write portable shell scripts. Writing a portable script should
not be that hard.
@@ -128,7 +128,7 @@ you will find with execline, and it is common to every script language.
The real solution to this portability problem is a convention that
guarantees fixed absolute paths for executables, which the FHS does not do.
-The slashpackage convention is
+The slashpackage convention is
such an initiative, and is well-designed; but as with every
convention, it only works if everyone follows it, and unfortunately,
slashpackage has not
@@ -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 ash shell seemed big, so I thought of writing my
own. Hence I had a look at the
-sh
+sh
specification... and ran away screaming.
This specification
is insane. It goes against every good programming
@@ -155,7 +155,7 @@ to wannabe sh 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
-gets
+gets
function, but this is the way it is.
diff --git a/doc/el_substitute.html b/doc/el_substitute.html
index 84b1985..3bb56a2 100644
--- a/doc/el_substitute.html
+++ b/doc/el_substitute.html
@@ -292,7 +292,7 @@ you can try to do better than these people:
Joël Riou
wrote the first execlineb quine, using
only echo as non-execline external command.
- Shortly after, Paul Jarc
+ Shortly after, Paul Jarc
wrote a much shorter quine, using
echo and env as non-execline external commands. He
also wrote a revised version, using only
diff --git a/doc/el_transform.html b/doc/el_transform.html
index f33c576..cb163a8 100644
--- a/doc/el_transform.html
+++ b/doc/el_transform.html
@@ -163,7 +163,7 @@ as n separate words.
- Netstrings are
+ Netstrings are
a way to reliably encode strings containing arbitrary characters.
execline takes advantage of this to offer a completely safe
splitting mechanism. If a substitution command is given an empty
diff --git a/doc/elglob.html b/doc/elglob.html
index 3df2541..0870d2d 100644
--- a/doc/elglob.html
+++ b/doc/elglob.html
@@ -31,7 +31,7 @@ another program.
- elglob performs
-globbing
+globbing
on pattern.
- It then performs
variable substitution on
diff --git a/doc/execline-cd.html b/doc/execline-cd.html
index 911eb2a..18759d1 100644
--- a/doc/execline-cd.html
+++ b/doc/execline-cd.html
@@ -31,7 +31,7 @@ given directory, then executes a program.
execline-cd performs a
-chdir()
+chdir()
system call on dir, then execs into prog....
diff --git a/doc/exitcodes.html b/doc/exitcodes.html
index 51902f1..619f5d3 100644
--- a/doc/exitcodes.html
+++ b/doc/exitcodes.html
@@ -30,7 +30,7 @@ to C, with as much precision as possible ?
The problem is, there's more information in a wstat (the
structure filled in by
-waitpid())
+waitpid())
than a process can report by
simply exiting. P could exit with the same exit code as C,
but then what should it do if C has been killed by a signal ?
@@ -52,7 +52,7 @@ can report.
Shells have their own
-convention
+convention
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/fdreserve.html b/doc/fdreserve.html
index cc808da..2412b5e 100644
--- a/doc/fdreserve.html
+++ b/doc/fdreserve.html
@@ -85,7 +85,7 @@ may fail, because oldfd and newfd may be the same.
To avoid that, you should make sure that all descriptors returned by
fdreserve are actually allocated before calling fdreserve
again.
-(Thanks to Paul Jarc for having
+(Thanks to Paul Jarc for having
spotted that case.)
diff --git a/doc/getcwd.html b/doc/getcwd.html
index 2f040db..9735630 100644
--- a/doc/getcwd.html
+++ b/doc/getcwd.html
@@ -43,7 +43,7 @@ execs into prog with its arguments.
- var must be given without a dollar !
- var must not contain =.
- Unlike the
-pwd
+pwd
POSIX command, getcwd does not depend on the PWD environment
variable and will exhibit a consistent behaviour no matter the environment.
diff --git a/doc/grammar.html b/doc/grammar.html
index de8f4cf..419c13e 100644
--- a/doc/grammar.html
+++ b/doc/grammar.html
@@ -38,8 +38,8 @@ instance, the nice command works that way:
nice -10 echo blah
will read nice and -10
from the argv, change the process' nice value, then exec into
the command echo blah. This is called
-chain loading
-by some people, and
+chain loading
+by some people, and
Bernstein chaining by others.
The purpose of the environment is to preserve some state across
execve() calls. This state is usually small: most programs
diff --git a/doc/index.html b/doc/index.html
index aa11b20..cb411a6 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -60,7 +60,7 @@ library.
execline is free software. It is available under the
-ISC license.
+ISC license.
Download
@@ -213,7 +213,7 @@ to your installation: the shebang lines for your system might be something like
Joël Riou. The only
external command used is echo.
Another quine, provided by
-Paul Jarc. It is much shorter, but
+Paul Jarc. It is much shorter, but
uses the external commands echo and env. Later, Paul rewrote
it using only echo, then
using only echo and the environment.
diff --git a/doc/multisubstitute.html b/doc/multisubstitute.html
index 99994df..aebdde8 100644
--- a/doc/multisubstitute.html
+++ b/doc/multisubstitute.html
@@ -110,7 +110,7 @@ substitutions, whereas parallel substitution pays the price only once.
Credits
-Paul Jarc first originated the
+Paul Jarc first originated the
idea of the multisubstitute command and a possible syntax.
diff --git a/doc/runblock.html b/doc/runblock.html
index b5cc65b..7e77102 100644
--- a/doc/runblock.html
+++ b/doc/runblock.html
@@ -74,7 +74,7 @@ an execline script, using the ifte command.
The runblock idea, as well as the ifelse idea, comes
-from Paul Jarc.
+from Paul Jarc.