From ab4da268c1643e55867adb10aa84ec38db24cbea Mon Sep 17 00:00:00 2001
From: Vidar Holen <vidar@vidarholen.net>
Date: Sun, 2 Dec 2018 13:20:32 -0800
Subject: [PATCH] Updated SC2154 (markdown)

---
 SC2154.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/SC2154.md b/SC2154.md
index 442ea1e..ebe1cc5 100644
--- a/SC2154.md
+++ b/SC2154.md
@@ -50,6 +50,6 @@ Note: This message only triggers for variables with lowercase characters in thei
 
 ### Exceptions:
 
-ShellCheck does not attempt to figure out runtime or dynamic assignments like with `source "$(date +%F).sh"` or `eval var=value`.
+ShellCheck intentionally does not attempt to figure out runtime or dynamic assignments like with `source "$(date +%F).sh"` or `eval var=value`. See [[SC2034]] for an extended discussion of why this is the case.
 
 If you know for a fact that the variable is set, you can use `${var:?}` to fail if the variable is unset (or empty), or explicitly initialize/declare it with `var=""` or `declare var`. You can also disable the message with a [[directive]].