3 SC2147

Vidar Holen edited this page 2015-10-03 21:33:27 -07:00

Table of Contents

• Literal tilde in PATH works poorly across programs.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions

Literal tilde in PATH works poorly across programs.

Problematic code:

PATH="$PATH:~/bin"

Correct code:

PATH="$PATH:$HOME/bin"

Rationale:

Having literal ~ in PATH is a bad idea. Bash handles it, but nothing else does.

This means that even if you're always using Bash, you should avoid it because any invoked program that relies on PATH will effectively ignore those entries.

For example, make may say foo: Command not found even though foo works fine from the shell and Make and Bash both use the same PATH. You'll get similar messages from any non-bash scripts invoked, and whereis will come up empty.

Use $HOME or full path instead.

Exceptions

If your directory name actually contains a literal tilde, you can ignore this message.

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.