2 SC2083

Joachim Ansorg edited this page 2022-10-31 15:25:58 +01:00

Table of Contents

• Don't add spaces after the slash in ./file.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

Don't add spaces after the slash in ./file.

Problematic code:

gcc -o myfile file.c
./ myfile

Correct code:

gcc -o myfile file.c
./myfile

Rationale:

Contrary to popular belief, there is no command or syntax ./ that runs a file.

./myfile is simply the shortest path equivalent to myfile that specifies a directory and therefore causes a shell to run it as-is, instead of trying to find its directory using $PATH.

Therefore, to run a file in the current directory, use ./myfile and not ./ myfile.

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.