Support iTerm2 Proprietary Escape Codes

[liamg]

Support iTerm2 Proprietary Escape Codes

[liamg]

Looking at the oh-my-zsh source, it looks like it's trying to add functionality for custom iterm2 escape codes, which I guess I'll have to either ignore or support. I haven't gone though the details yet, but it's basically this stuff.

[liamg]

Hmm, I can't reproduce this with zsh on Ubuntu, I'll try on my Mac tomorrow.

[zac-garby]

I'm getting the same error.

• macOS Mojave 10.14.1 Beta (18B73a)
• go version go1.11 darwin/amd64

[liamg]

What version of zsh are you using? I can't reproduce with zsh 5.3 (x86_64-apple-darwin17.0)

[jamesnetherton]

I see the same error with zsh 5.3.1 (x86_64-debian-linux-gnu). If I stop sourcing oh-my-zsh in my .zshrc, the error goes away.

[jcarter3]

I get the same error with zsh 5.6.2 (x86_64-apple-darwin17.7.0)

[mikechernev]

Could this be related to the oh-my-zsh or its themes?
I get the error as well, although I don't see any impact on the functionality or the performance.

macOS High Sierra (10.13.6)
zsh 5.3 (x86_64-apple-darwin17.0)

[liamg]

Yeah, it's sending an OSC code that I can't find documented anywhere. It's not a major issue, but I'd like to find out what oh-my-zsh is trying to do and whether we can support it.

[beaugunderson]

i got a ton of these (and no screen output) the first time I launched as well; in my case they're definitely from iTerm 2 integration and truecolor