2 SC1141

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

Table of Contents

• Unexpected tokens after compound command. Bad redirection or missing ;/&&/||/|?
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

Unexpected tokens after compound command. Bad redirection or missing ;/&&/||/|?

Problematic code:

while echo "$2"; do true; done \
  head -n "$1"

while sleep 1; do date; done > my file

Correct code:

while echo "$2"; do true; done \
  | head -n "$1"

while sleep 1; do date; done > "my file"

Rationale:

ShellCheck found unexpected trailing characters after a compound command.

The only things allowed after compound commands are redirections, shell keywords, and the various command separators (;, &, |, &&, ||).

In the first example, a | was missing, causing head to appear as an unexpected trailing word, instead of being piped to. In the second example, a lack of quoting caused file to appear as an unexpected trailing word, instead of being part of the redirection.

Examine your statement and correct the problem.

Exceptions:

None

Related resources:

• Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!

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.