2 SC3004

Vidar Holen edited this page 2021-07-24 22:23:16 -07:00

Table of Contents

• In POSIX sh, $".." is undefined
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

In POSIX sh, $".." is undefined

Problematic code:

printf $"Hello, %s\n" "$USER"

Correct code:

# Check if gettext exists
if ! type gettext > /dev/null 2>&1
then
  # If not, create a dummy function that returns the input verbatim
  gettext() { printf '%s' "$1"; }
fi

# Use gettext to get a translated version of the string
printf "$(gettext 'Hello, %s\n')" "$USER"

Rationale:

Bash allows using $"..." to easily get a translated string according to the current locale. This is powered by the gettext infrastructure.

Neither $".." nor the gettext infrastructure or the gettext command is POSIX. A script targeting sh may choose to invoke gettext if the system has it (such as GNU or Solaris), or use the translated string verbatim if it doesn't (such as macOS or FreeBSD).

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.