Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dart VM output window in the Dart Editor should handle escape sequence for colors #4654

Closed
terrylucas opened this issue Aug 22, 2012 · 9 comments
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug

Comments

@terrylucas
Copy link
Contributor

Output when running an app Dart command line launch in the editor should handle escape sequence for Linux shell colors.

See http://linuxshellaccount.blogspot.com/2008/03/using-color-in-linux-or-unix-shell.html

for example:

    String GREEN_COLOR = '\u001b[32m';
    String NO_COLOR = '\u001b[0m';
    print("Parsed ${GREEN_COLOR}main.html${NO_COLOR}in 23 msec.");

Would display the text in a Linux shell as:

             Parsed main.html in 23 msec.

where "main.html" would be green and the rest of the text is black.

Nice so that rich tools that return errors in red, warnings in yellow, etc. can be written to look nice in the editor's Command Line window. Instead of looking:

� Parsed [32mmain.html�[0m in 23 msec.

@stevemessick
Copy link
Contributor

Set owner to @devoncarew.
Added this to the Later milestone.
Removed Type-Defect label.
Added Type-Enhancement, Triaged labels.

@devoncarew
Copy link
Member

Removed this from the Later milestone.
Added this to the M3 milestone.

@danrubel
Copy link

Removed this from the M3 milestone.
Added this to the Later milestone.

@devoncarew
Copy link
Member

Issue #10080 has been merged into this issue.

@devoncarew
Copy link
Member

Removed the owner.
Added PatchesWelcome label.

@stevemessick
Copy link
Contributor

Issue #6140 has been merged into this issue.

@kasperl
Copy link

kasperl commented Jul 10, 2014

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

@sethladd
Copy link
Contributor

Added NotPlanned label.

@clayberg
Copy link

Added this to the 1.6 milestone.

@terrylucas terrylucas added Type-Enhancement closed-not-planned Closed as we don't intend to take action on the reported issue labels Aug 13, 2014
@terrylucas terrylucas added this to the Oldschool-Later milestone Aug 13, 2014
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

8 participants