From 4bc88148687f3732a2e67711d2c3fd5e46d6c9cf Mon Sep 17 00:00:00 2001 From: TurdPooCharger <35666439+TurdPooCharger@users.noreply.github.com> Date: Sat, 21 Apr 2018 20:25:45 -0400 Subject: [PATCH] GitHub formatting is problematic conveying sentences with proper line breaking. Will need to discuss solution. --- Scripting:--echo.md | 37 ++++++++++++++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/Scripting:--echo.md b/Scripting:--echo.md index 640780b..fc65ad1 100644 --- a/Scripting:--echo.md +++ b/Scripting:--echo.md @@ -6,7 +6,7 @@ Including the blank space ` `, these are the available char. ` ` `!#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_``abcdefghijklmnopqrstuvwxyz{|}~` ### Implicit vs Explicit Statements -Simple one worded phrases may employ the implicit method of `echo` statements. +In general, one worded, simple, or continuous phrases may be implicitly stated. **Example 1:** `echo Hello` @@ -16,7 +16,7 @@ Simple one worded phrases may employ the implicit method of `echo` statements. There are limitations for phrases containing certain char, including ` ` `-#$%` -Explicitness necessitates the usage of quotation marks `" "`. +These phrases fall under the explicit category in which quotation marks `" "` are necessary. **Example 3:** @@ -24,7 +24,38 @@ Incorrect: `echo Hello World` Correct: `echo "Hello World"` +**Example 4:** + +Incorrect: `echo 0:/Nintendo 3DS/` + +Correct: `echo "0:/Nintendo 3DS/"` + ### Skipping lines -`\n` + +Phrases that are too long may become unreadable if they fill past the right edge of the 3DS bottom screen. Like typing with the **Enter** key for a keyboard, the inclusion of `\n` serves as a break to begin readouts with a new line. + +**Example 5:** +echo "Hello \nWorld" + +Hello + +World + +In order to skip two lines, care is needed to add ` ` between the two `\n`. + +**Example 6:** + +`echo "Hello \n\nWorld"` + +Hello + +World + +**Example 7:** + +`echo "Hello \n \nWorld"` + +Hello +World \ No newline at end of file