mirror of
https://github.com/koalaman/shellcheck.git
synced 2025-10-03 19:29:44 +08:00
Updated SC1117 (markdown)
10
SC1117.md
10
SC1117.md
@@ -1,5 +1,7 @@
|
|||||||
## Backslash is literal in `"\n"`. Prefer explicit escaping: `"\\n"`.
|
## Backslash is literal in `"\n"`. Prefer explicit escaping: `"\\n"`.
|
||||||
|
|
||||||
|
**Note: this warning has been retired due to being too pedantic**
|
||||||
|
|
||||||
### Problematic code:
|
### Problematic code:
|
||||||
|
|
||||||
```sh
|
```sh
|
||||||
@@ -26,6 +28,10 @@ Instead of relying on this implicit fallback, you should escape the backslash ex
|
|||||||
|
|
||||||
### Exceptions:
|
### Exceptions:
|
||||||
|
|
||||||
None. This is a stylistic issue which can be [[ignore]]d.
|
None. This is a stylistic issue which can be [[ignore]]d. But can you name the 5 characters that *are* special when escaped in double quotes?
|
||||||
|
|
||||||
Before you do -- can you name the 5 characters that *are* special when escaped in double quotes?
|
### Retired:
|
||||||
|
|
||||||
|
This warning is no longer emitted as of d8a32da07 (strictly after v0.5).
|
||||||
|
|
||||||
|
The number of harmlessly affected `printf`, `sed` and `grep` statements was significantly higher than the number of actual unexpanded escape sequences. It may return some day under a `-pedantic` type flag.
|
Reference in New Issue
Block a user