> ## Documentation Index > Fetch the complete documentation index at: https://docs.syntblaze.com/llms.txt > Use this file to discover all available pages before exploring further. # Bash Negated Pipeline A negated pipeline in Bash is a pipeline prefixed with the `!` reserved word, which logically inverts the final exit status (`$?`) of the executed command sequence. If the underlying pipeline evaluates to a zero exit status (success), the negation forces an exit status of `1`. Conversely, if the pipeline evaluates to a non-zero exit status (failure), the negation forces an exit status of `0`. ## Syntax ```bash theme={"dark"} ! command [ | command2 ... ] ``` ## Technical Mechanics * **Reserved Word Parsing:** The `!` character is parsed as a shell reserved word, not a built-in or external command. It must appear at the beginning of the pipeline and must be separated from the subsequent command by whitespace. Without the trailing space, the interactive shell parser will interpret it as a history expansion directive (e.g., `!command`). Control operators immediately following `!` will either cause a syntax error (e.g., `!|cmd`) or terminate the pipeline entirely (e.g., `!;cmd`). Additionally, while `(` is a control operator, `!(` is tokenized as an extended glob pattern in Bash, meaning a space is strictly required to negate a subshell (e.g., `! (cmd)`). * **Exit Status Mapping:** * Original pipeline exit status `0` -> Negated pipeline exit status `1`. * Original pipeline exit status `N` (where `N > 0`) -> Negated pipeline exit status `0`. * **Multi-Command Pipeline Evaluation:** In a pipeline containing multiple commands (`! cmd1 | cmd2`), the negation applies to the final evaluated exit status of the entire pipeline. By default, this is the exit status of the last command (`cmd2`). If the `pipefail` shell option is enabled, the pipeline's pre-negation status is the exit status of the rightmost command to exit with a non-zero status, or `0` if all commands in the pipeline exit successfully. The `!` reserved word then inverts that final resolved integer. * **Interaction with `errexit`:** Bash explicitly exempts any pipeline prefixed with `!` from `errexit` (`set -e`) termination. This exemption is a syntactic rule of the shell's error handling, independent of the final inverted exit status. For example, the pipeline `! true` evaluates to an exit status of `1` (a failure), but it will not cause the script to terminate under `set -e` because the `!` reserved word explicitly suppresses the `errexit` evaluation for that pipeline. * **Subshell Execution Context:** While each command within a standard multi-command pipeline executes in its own subshell by default (unless the `lastpipe` option is enabled), the `!` reserved word itself does not alter this behavior or introduce an additional subshell environment. The negation operation occurs in the parent shell environment after the pipeline's execution completes, simply inverting the returned integer.

Tired of Poor Bash Skills? Fix That With Deep Grasping! Learn More