2 SC2189

Joachim Ansorg edited this page 2021-11-12 19:46:05 +01:00

Table of Contents

• You can't have | between this redirection and the command it should apply to.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:

You can't have | between this redirection and the command it should apply to.

Problematic code:

< file.txt | grep foo

Correct code:

< file.txt grep foo   # or more canonically: grep foo < file.txt

Rationale:

ShellCheck has found a stage in a pipeline that consists of a redirection but no command. This doesn't make sense because a redirection without a command will not read or write any data.

This is most likely to occur when deleting a command that had a redirection, but leaving a | behind instead of moving the redirection to a different command:

# Match lines with line numbers
nl < foo.txt | grep bar

# Incorrect attempt at removing line numbers. grep now has no input:
< foo.txt | grep bar

# Line numbers correctly removed. grep now reads foo.txt as intended.
grep bar < foo.txt

Exceptions:

It's technically valid to do e.g. echo foo | > "$(cat)" to truncate a file called "foo", but please consider rewriting such code.

ShellCheck

• Installation

  • CentOS6
  • More Installation Guides

• Usage

  • Directive
  • Ignore

• Integrating and extending

  • Misc. contributions
  • Azure Pipelines
  • Buildkite
  • CircleCI
  • DevGuide
  • Integration
  • JUnit
  • Phabricator
  • TravisCI
  • GitLab CI
  • Drone
  • GitHub Actions

• Severity

• Template

Each individual ShellCheck warning has its own wiki page like SC1000. Use GitHub Wiki's "Pages" feature above to find a specific one, or see Checks.