New Code Causes Prompt to Blow Up

[jkrot]

I am running this on a mac and using the new code my prompt looks like, going back a commit and it looks fine.

[dmccaffery]

Seconded. Definitely an issue on OS X currently.

[lyze]

I won't have access to a Mac until tomorrow, so I can't debug the issue yet. In the meantime, what does the output look like if ANSI color interpretation is disabled in the terminal settings? I'm guessing this happens on the (old 3.x) bash that ships with OSX by default?

[dmccaffery]

GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)
Copyright (C) 2007 Free Software Foundation, Inc.

Thats the version of bash that I am using. It is quite old. I'll have to reinstall the latest bits and disable ANSI to get back to you re: what the output looks like without ANSI.

[dmccaffery]

Before (ANSI):

After (ANSI):

ANSI disabled:

Does not emit the ANSI color codes when disabling ANSI... OS X terminal just swallows them, it would appear. I tried changing the TERM as well to no effect.

The prompt is set using the following script (part of my prompt kit):
https://github.com/pulsebridge/uber/blob/master/src/scripts/set-prompt.sh

[lyze]

I think 8d28204 should fix things. I promise I do know how to get a backslash to show up with echo... 😿 I can check for sure later when I get to a Mac.

[dmccaffery]

@lyze confirmed -- 8d28204 works for me.

[dmccaffery]

Proof:

[lyze]

Works for me too! Closing.