Debug terminal - interpret 0x08 char as backspace

Completed

Comments

6 comments

  • Avatar
    Anthony Verbeck

    I agree with this completely.

    And while at it, add ANSI color codes too!

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    ANSI color codes are in fact supported, for example:

      debug_printf("\x1B[31mRed\n");
      debug_printf("\x1B[32mGreen\n");
      debug_printf("\x1B[34mBlue\n");

    I agree that propeller/twirly support is limited, I'll look into improving this situation.

    Regards,

    Jon

     

    0
    Comment actions Permalink
  • Avatar
    Anthony Verbeck

    Jon,

    You're right -- it's there.

    Years ago I wrote a trace library that used various colors to represent issues: green=logging, yellow=warning, red=bad, bad, bad. You could just look at the terminal trace to see how a system was running.  Now, I can port this to CrossWorks.

    Thanks,

    ACV

    0
    Comment actions Permalink
  • Avatar
    Joe Merten

    Ansi colors won't work in my setup (but they are working using minicom).

    My code:

        Console::writeLine("\x1B[31mRed");
        Console::writeLine("\x1B[32mGreen");
        Console::writeLine("\x1B[34mBlue");
    Terminal output:

        1mRed
        2mGreen
        4mBlue

    Cheers, Joe

    0
    Comment actions Permalink
  • Avatar
    Jon Elliott

    Hi Joe,

    I've just tried it and you're quite right, escape sequences are working in the debug terminal but not in the terminal emulator. I'll see this gets fixed in the next release.

    Regards,

    Jon

    0
    Comment actions Permalink
  • Avatar
    Joe Merten

    Well, also a bit missunderstanding of mine - I had not realized the difference between "Debug Terminal" and "Terminal Emulator" - until now.

    Thanks for clarifying.

    0
    Comment actions Permalink

Please sign in to leave a comment.