From 68756357363cf3260a0af8ed5efa04105bab17e7 Mon Sep 17 00:00:00 2001 From: Vidar Holen Date: Thu, 26 Jul 2018 19:48:13 -0700 Subject: [PATCH] Updated SC1117 (markdown) --- SC1117.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/SC1117.md b/SC1117.md index 0b85435..16dbdf0 100644 --- a/SC1117.md +++ b/SC1117.md @@ -1,5 +1,7 @@ ## Backslash is literal in `"\n"`. Prefer explicit escaping: `"\\n"`. +**Note: this warning has been retired due to being too pedantic** + ### Problematic code: ```sh @@ -26,6 +28,10 @@ Instead of relying on this implicit fallback, you should escape the backslash ex ### 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? \ No newline at end of file +### 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. \ No newline at end of file