10

SC1007

wileyhy edited this page 2024-10-05 22:33:19 -07:00

Table of Contents

• Remove space after = if trying to assign a value (or for empty string, use var="" ... ).
• Problematic code:
• Correct code:
• Rationale:
• Exceptions
• Related Resources:

Remove space after = if trying to assign a value (or for empty string, use var="" ... ).

Problematic code:

# I want programs to show text in Dutch!
LANGUAGE= nl

# I want to run the nl command with English error messages!
LANGUAGE= nl

Correct code:

# I want programs to show text in Dutch!
LANGUAGE=nl

# I want to run the nl command with English error messages!
LANGUAGE='' nl

Rationale:

It's easy to think that LANGUAGE= nl would assign "nl" to the variable LANGUAGE. It doesn't.

Instead, it runs nl (the "number lines" command) and sets LANGUAGE to an empty string in its environment.

Since trying to assign values this way is a common mistake, ShellCheck warns about it and asks you to be explicit when assigning empty strings (except for IFS, due to the common IFS= read .. idiom).

Exceptions

If you're familiar with this behavior and feel that the explicit version is unnecessary, you can ignore it.

Related Resources:

https://www.gnu.org/software/bash/manual/html_node/Shell-Parameters.html https://mywiki.wooledge.org/BashPitfalls#foo_.3D_bar

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.