On Wed, Oct 9, 2013 at 5:28 PM, Graham Leggett <minfrin@sharp.fm> wrote:
On 09 Oct 2013, at 10:34 PM, Jeff Trawick <trawick@gmail.com> wrote:

> The function is trying to escape any binary values that could conceivably cause problems when printed to the terminal, whether or not those values happen to have a C escape sequence "shortcut".  The escaping is done regardless IIUC.  It looks like the code which uses \e is just trying to use well-known shortcuts for certain escape sequences, and if the \e code is removed then it will use the hex equivalent.

This is true.

I have backported the API in r1530799, would it be possible to take a look for me?

Work fine for me with the cmake-based build on Windows (MSVC).



Born in Roswell... married an alien...