I/O garbled in Xcode's "pseudo" PTY

[mralexgray]

you DID say to test it everywhere.... and although the Xcode console is far from compliant with ANYthing.. it would be nice if there was a sane way to interact with it.. which is what led me to your (neat) project.

everything is fine and dandy in iTerm...

but here's what happens in good'ole Xcode (6.1.1)...

arguably, this IS better (though far from ideal)... than what you get with my normal IO routines in the same console environment...

The Xcode console is very weird.. It has no exposed "size" (COLUMNS, and the such), and also, mine MAY be off kilter a bit.. as I DO have the XCODE_COLORS extension installed (amongst many others). Maybe someone with a stock rig can try it, as well?

Let me know how I can help fix this... if you (and God, 🙏) are wiling...

[antirez]

Hello! If you tested with the latest commit of Linenoise (very likely), it is going to be very hard to fix, because it uses really the bare minimum of pure VT100 capabilities! So likely there is really no decent VT100 support at all in the XCode console :-) Thanks for reporting and for the nice gifs.

[mralexgray]

I'm going to look into it. I didn't mean to sound hopeless.. I mean it almost works. I will fiddle with it and see if I can't muster a more usable state with minimal change required.

[iliaskarim]

@mralexgray I would love to see this 👍

[xrdavies]

The same issue met, not able to debug with xcode 9.2 console.
Really helpless on this when wanna try to replace readline lib.

[fosterbrereton]

Gah! This library is this close -> <- to what I want, but since I cannot use it in Xcode, I'm afraid I cannot use it. If this ever does get resolved (even if that means a reduced feature set when inside Xcode), it would be amazing.

[fosterbrereton]

A workaround I found was to change isUnsupportedTerm to return 1 instead of 0 in the event there is no TERM environment variable. This at least makes the Xcode terminal functional, though it will still be lacking many features.