2 SC1082

Joachim Ansorg edited this page 2021-11-12 10:45:23 +01:00

Table of Contents

• This file has a UTF-8 BOM. Remove it with: LC_CTYPE=C sed '1s/^...//' < yourscript.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:

This file has a UTF-8 BOM. Remove it with: LC_CTYPE=C sed '1s/^...//' < yourscript.

Problematic code:

This is an encoding error that can't be seen in the script itself, but cat -v will show three bytes of garbage at the start of the file:

$ cat -v file
M-oM-;M-?#!/bin/bash
echo "hello world"

Correct code:

The code is correct when this garbage does not appear.

Rationale:

Some editors may save a file with a Byte Order Mark to mark the file as UTF-8. Shells do not understand this and will give errors on the first line:

$ bash myscript
myscript: line 1: #!/bin/sh: No such file or directory

$ dash myscript
myscript: 1: myscript: #!/bin/sh: not found

To fix it, remove the byte order mark. One way of doing this is LC_CTYPE=C sed '1s/^...//' < yourscript. Verify that it's not there with cat -v.

Exceptions:

None

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.