5 SC1077

Joachim Ansorg edited this page 2021-11-12 10:44:42 +01:00

Unescape Escape

Table of Contents

• For command expansion, the tick should slant left (` vs ´).
• Problematic code:
• Correct code:
• Rationale:
• Exceptions

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

For command expansion, the tick should slant left (` vs ´).

Problematic code:

echo "Your username is ´whoami´"

Correct code:

echo "Your username is $(whoami)" # Preferred
echo "Your username is `whoami`"  # Deprecated, will give [SC2006]

Rationale:

In some fonts it's hard to tell ticks apart, but Bash strongly distinguishes between backticks (grave accent `), forward ticks (acute accent ´) and regular ticks (apostrophe ').

Backticks start command expansions, while forward ticks are literal. To help spot bugs, ShellCheck parses backticks and forward ticks interchangeably.

Exceptions

If you want to write out literal forward ticks, such as fancyful ascii quotation marks:

echo "``Proprietary software is an injustice.´´  - Richard Stallman"

use single quotes instead:

echo '``Proprietary software is an injustice.´´  - Richard Stallman'

To nest forward ticks in command expansion, use $(..) instead of `..`.

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.