From d5aed446711bb6436f8a1c47d02527a2af0e6d15 Mon Sep 17 00:00:00 2001 From: Ryan Jacobs Date: Tue, 26 Feb 2019 13:16:06 -0800 Subject: [PATCH] bugfix: Replace echo with printf so "\n" renders. notes: I could have used the -e flag in echo, however other lines nearby use printf so I figured it would be smart to stay consistent. Also, I see the usage of `command printf`. Not 100% if this is necessary. I don't see why printf would be redefined in the shell. If we're doing this, then we might as well prefix every call to a builtin or binary with `command` _just to be safe_. --- install.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/install.sh b/install.sh index 04b5f364a..0b7da4ca2 100755 --- a/install.sh +++ b/install.sh @@ -133,7 +133,7 @@ wasmer_link() { SOURCE_STR="# Wasmer config\nexport WASMER_DIR=\"\$HOME/.wasmer\"\nexport WASMER_CACHE_DIR=\"\$WASMER_DIR/cache\"\nexport PATH=\"\$HOME/.wasmer/bin:\$PATH\"\n" # We create the wasmer.sh file - echo "$SOURCE_STR" > "$HOME/.wasmer/wasmer.sh" + printf "$SOURCE_STR" > "$HOME/.wasmer/wasmer.sh" if [ -z "${WASMER_PROFILE-}" ] ; then printf "${red}Profile not found. Tried:\n* ${WASMER_PROFILE} (as defined in \$PROFILE)\n* ~/.bashrc\n* ~/.bash_profile\n* ~/.zshrc\n* ~/.profile.\n"