mirror of https://github.com/tLDP/LDP
Changed – to — in several places. Minor rewording of prose in the
"Variables" section.
This commit is contained in:
parent
bac7a21d7f
commit
9a04863994
|
@ -379,7 +379,7 @@ Hello world
|
|||
and executes the command "<computeroutput><command>bash
|
||||
hello</command></computeroutput>". The other is the non-interactive Bash
|
||||
shell that you manually started to execute the script. The interactive
|
||||
shell isn't doing anything while the script is running – it's merely
|
||||
shell isn't doing anything while the script is running — it's merely
|
||||
waiting for the non-interactive shell to terminate. In <xref
|
||||
linkend="ex-running-hello"/>, the interactive shell is Bash, but you don't
|
||||
have to use Bash as your interactive shell to run a Bash script. The
|
||||
|
@ -841,7 +841,7 @@ two lines"
|
|||
of that command, your interactive shell doesn't execute the command.
|
||||
Instead, it notices that you have not typed a closing double quote, and
|
||||
prompts you to continue entering the command. Only when a complete
|
||||
command – with a balanced set of double quotes – has been
|
||||
command — with a balanced set of double quotes — has been
|
||||
entered, will pressing the <keysym>ENTER</keysym> key execute the command.
|
||||
You can write the above command in a shell script too, and it will behave
|
||||
the same way.
|
||||
|
@ -888,7 +888,7 @@ echo *
|
|||
This happens because the asterisk is a Bash wildcard metacharacter, and
|
||||
Bash replaces each word containing an asterisk with a list of matching file
|
||||
and directory names before executing the command. You want Bash to treat
|
||||
the asterisk as if it were just an ordinary character – not a
|
||||
the asterisk as if it were just an ordinary character — not a
|
||||
metacharacter. To do this, you use double quotes to
|
||||
<firstterm>escape</firstterm> (or <firstterm>quote</firstterm>) the
|
||||
asterisk as follows:
|
||||
|
@ -1081,7 +1081,7 @@ My home directory is $HOME
|
|||
As you can see, both single and double quotes escape the
|
||||
"<computeroutput>*</computeroutput>" metacharacter, but only single quotes
|
||||
are powerful enough to escape the "<computeroutput>$</computeroutput>"
|
||||
metacharacter (which is used to expand variables – we'll cover
|
||||
metacharacter (which is used to expand variables — we'll cover
|
||||
variables in <xref linkend="sect-variables"/>).
|
||||
</para>
|
||||
|
||||
|
@ -1185,7 +1185,7 @@ Welcome to Frodo's Place!
|
|||
<title>Variables</title>
|
||||
|
||||
<para>
|
||||
A variable is a name for a memory location where a shell script can store
|
||||
A variable is a name for a place in memory where a shell script can store
|
||||
a string of characters. Those characters can be anything, including
|
||||
letters, digits, punctuation, spaces and tabs. In the following sections,
|
||||
we discuss how to assign values to variables and how to access those
|
||||
|
|
Loading…
Reference in New Issue