Pipes render incorrectly in iterm2

[alexholliz]

Running pipes.sh from iterm2-nightly Build 3.3.20190405-nightly on mac. Installed 1.3.0 via homebrew. When invoking pipes.sh it prints \e[1m\e[32m next to every "pipe" character. It also does not print in color.

Running ZSH

echo $TERM
xterm-256color

locale
LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=

[j3r1ch0]

I know this is super old but I figured I'd answer anyway. It's not iterm2 that is the problem. The problem is your ZSH shell. This is a Bash script, written for use in a Bash shell. ZSH is close to Bash, but varies in some subtle ways. If you first type bash before invoking the pipes.sh script it should work just fine since it'll drop you in to a Bash shell.

[lovetoburnswhen]

I know this is super old but I figured I'd answer anyway. It's not iterm2 that is the problem. The problem is your ZSH shell. This is a Bash script, written for use in a Bash shell. ZSH is close to Bash, but varies in some subtle ways. If you first type bash before invoking the pipes.sh script it should work just fine since it'll drop you in to a Bash shell.

I'm getting the same issue unfortunately with bash pipes.sh.

Using cpipes works great

[MXCR-cpu]

Leaving this here for possible future reference. I have found that one work around is to change echo -n to printf in the script's main function for-loop. I tried the to find a good justification for this but came up empty handed: so far the working theory is that it has something to do with echo failing to accept the escape character.