2

SC1101

Joachim Ansorg edited this page 2021-11-12 18:53:39 +01:00

Table of Contents

• Delete trailing spaces after \ to break line (or use quotes for literal space).
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:

Delete trailing spaces after \ to break line (or use quotes for literal space).

Problematic code:

# There are spaces after the backslash:
echo hello \  
     world

Correct code:

# No spaces after the backslash:
echo hello \
     world

Rationale:

To break a line you can use \ before the line break. However, if there are spaces after the backslash, the escape will apply to them instead of the line break, and the command will not continue on the next line.

Delete the trailing spaces to make the line break work correctly.

Exceptions:

If you do want a literal escaped space at the end of a line you can ignore this error, but please reconsider and use quotes instead. Trailing whitespace is invisible and frequently stripped on purpose (by editor settings / precommits) or accident (copy-paste), and so should not be relied upon for correctness.

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.