From 7bc5da0e36f1e253a1258169665b8ba5063e173a Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Wed, 22 Jan 2020 14:12:56 -1000 Subject: [PATCH] Update 03_3__Interlude_Using_Command-Line_Variables.md --- 03_3__Interlude_Using_Command-Line_Variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/03_3__Interlude_Using_Command-Line_Variables.md b/03_3__Interlude_Using_Command-Line_Variables.md index dfed3a7..11eaa68 100644 --- a/03_3__Interlude_Using_Command-Line_Variables.md +++ b/03_3__Interlude_Using_Command-Line_Variables.md @@ -1,6 +1,6 @@ # Interlude: Using Command-Line Variables -> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. +> :information_source: **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. The previous section demonstrated a number of command-line commands used without obfuscation or interference. However, that's often not the best way to run Bitcoin from the command line. Because you're dealing with long, complex, and unreadable variables, it's easy to make a mistake if you're copying those variables around (or, satoshi forfend, if you're typing them in by hand). Because those variables can mean the difference between receiving and losing real money, you don't _want_ to make mistakes. For these reasons, we strongly suggest using command-line variables to save addresses, signatures, or other long strings of information whenever it's reasonable to do so.