ksh/ksh.1:Note that
ksh/ksh.1:Note that any unquoted space before and after a pattern is
ksh/ksh.1:Note that redirections specified after a function definition are
ksh/ksh.1:Note that changing the
ksh/ksh.1:Note that if the
ksh/ksh.1:Note that
ksh/ksh.1:Note that both the parameter name and the
ksh/ksh.1:Note that if
ksh/ksh.1:Note that since the command-line editors try to figure out how long
the prompt
ksh/ksh.1:Note that the backslash itself may be interpreted by the shell.
ksh/ksh.1:Note that none of the above pattern elements match either a period
ksh/ksh.1:Note that this means the command
ksh/ksh.1:Note that this behaviour is slightly
ksh/ksh.1:Note that if a command is not found using
ksh/ksh.1:Note that special parameters (e.g.\&
ksh/ksh.1:Note that
ksh/ksh.1:Note that the Bourne shell differs here;
ksh/ksh.1:Note that
ksh/ksh.1:Note that setting this option does not affect the current value of the
ksh/ksh.1:Note that some special rules are applied (courtesy of POSIX)
ksh/ksh.1:Note that the output of
ksh/ksh.1:Note that for
ksh/ksh.1:Note that only commands that create processes (e.g. asynchronous
commands,
ksh/ksh.1:Note that editing command names are used only with the
ksh/ksh.1:Note that the ^X stands for control-X; also
To pick one example
{ list; }
Compound construct; list is executed, but not in a subshell.
Note that `{' and `}' are reserved words, not meta-characters.
What would be wrong with saying it like this?
{ list; }
Compound construct; list is executed, but not in a subshell.
`{' and `}' are reserved words, not meta-characters.
Hang on, I'm finding a piece of paper to make a note. Apparently this
2nd sentence is very important, the requirement I make a note of it must
mean it is more important than the 1st sentence!