From 5c927dcdfeb828d274e26a6dafed7f0649077945 Mon Sep 17 00:00:00 2001
From: Vidar Holen <vidar@vidarholen.net>
Date: Tue, 1 Sep 2020 17:47:48 -0700
Subject: [PATCH] Created SC3038 (markdown)

---
 SC3038.md | 37 +++++++++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 SC3038.md

diff --git a/SC3038.md b/SC3038.md
new file mode 100644
index 0000000..ec5ff8b
--- /dev/null
+++ b/SC3038.md
@@ -0,0 +1,37 @@
+## In POSIX sh, exec flags are undefined.
+
+(or "In dash, ... are not supported." when using `dash`)
+
+### Problematic code:
+
+```sh
+#!/bin/sh
+exec -ca ls busybox
+```
+
+### Correct code:
+
+Switch to a shell that does support the `exec` flags you are using, like `bash`:
+
+```sh
+#!/bin/bash
+exec -ca ls busybox
+```
+
+In POSIX, you can use `env` to start a command with a clean environment, but there is no way to generally specifying the zeroth argument.
+
+### Rationale:
+
+Flags to `exec` are bash and ksh extensions. `dash` and POSIX `sh` does not support them.
+
+### Exceptions:
+
+If you only intend to target shells that supports this feature, you can change
+the shebang to a shell that guarantees support, or [[ignore]] this warning.
+
+You can use `# shellcheck disable=SC3000-SC4000` to ignore all such compatibility
+warnings.
+
+### Related resources:
+
+* Help by adding links to BashFAQ, StackOverflow, man pages, POSIX, etc!