Results 1 - 17 of about 17 results out of about 57127 pages. (0.02 seconds)
- Handling_contents_of_files . . . 2 matches
- ...
}}}
This example uses [[BASH]] and KornShell ArithmeticExpressions, which older [[BourneShell|Bourne shells]] do not have. In that case the following example should be used inst...
- ShellHallOfShame . . . 1 match
- ...hance.)
There is, in general, no clean way to handle this problem in the classic [[BourneShell|Bourne shell]]. But HP wasn't limited to the use of the Bourne shell when they wro...
- KornShell . . . 1 match
- ...= Korn Shell =
The KornShell is a reimplementation of the [[BourneShell|Bourne shell]]. It is downward compatible, but adds many features intended to simplify programming. Most of...
- FullBashFAQ . . . 1 match
- ...the man pages or the GNU info pages as the authoritative references.
[[BASH]] is a BourneShell compatible shell, which adds many new features to its ancestor. Most of them are av...
- CommandSubstitution . . . 1 match
- ...'`)` syntax is supported by KornShell, [[BASH]], and PosixShell. Older shells (e.g. BourneShell) use the following syntax: {{{`command`}}}. Note that these are not the apostrophe ...
- BashGuide/InputAndOutput . . . 1 match
- ... file' &> proud.log
}}}
This is the same as `> proud.log 2>&1`, but not portable to BourneShell. It is not recommended practice, but you should recognize it if you see it used in...
- BashFAQwTopics . . . 1 match
- ...the man pages or the GNU info pages as the authoritative references.
[[BASH]] is a BourneShell compatible shell, which adds many new features to its ancestor. Most of them are av...
- BashFAQ/082 . . . 1 match
- ...|command substitution]], required by only the very oldest of non-POSIX-compatible [[BourneShell|Bourne shells]]. There are several reasons to always prefer the {{{$(...)}}} syntax...
- BashFAQ/074 . . . 1 match
- ...he extended forms of [[BashFAQ/073|parameter expansion]] do not work with the older BourneShell. If your code needs to be portable to that shell as well, {{{sed}}} and {{{expr}}} ...
- BashFAQ/041 . . . 1 match
- ...[[BashFAQ/100|FAQ #100]].
If you are programming in the POSIX sh syntax or for the BourneShell instead of Bash, there is a more portable (but less pretty) syntax:
{{{
# Bourne...
- BashFAQ/031 . . . 1 match
- ...} be used, and when the old one {{{[}}}? If portability/conformance to POSIX or the BourneShell is a concern, the old syntax should be used. If on the other hand the script requir...
- BashFAQ/025 . . . 1 match
- ...} }}}instead of {{{$10}}}. This works for [[BASH]] and KornShell, but not for older BourneShell implementations. Another way to access arbitrary positional parameters after $9 is ...
- BashFAQ/024 . . . 1 match
- ...`echo` command.
Different shells exhibit different behaviors in this situation:
* BourneShell creates a subshell when the input or output of anything (loops, case etc..) but a s...
- BashFAQ/019 . . . 1 match
- ...
The previous example uses POSIX [[ArithmeticExpression|arithmetic]], which older [[BourneShell|Bourne shells]] do not have. In that case the following example should be used inst...
- BashFAQ/018 . . . 1 match
- ...nBSD (at least)
jot -w %02d 10 1
}}}
Finally, the following example works with any BourneShell derived shell (which also has `expr` and `sed`) to zero-pad each line to three byte...
- BashFAQ/005 . . . 1 match
- ...are not specified by POSIX and not available in legacy or minimalist shells such as BourneShell and Dash. The POSIX-compatible shells that do feature arrays mostly agree on their ...
- BashFAQ . . . 1 match
- ...the man pages or the GNU info pages as the authoritative references.
[[BASH]] is a BourneShell compatible shell, which adds many new features to its ancestor. Most of them are av...