Nothing to add. Works marvelous. If you observe washed colors in Windows (against vivid in the Windows 10 command prompt) you can switch color palette in preferences. I observe xterm as closest to these in command prompt
I love the pluggin, works great, except for 1 small issue.
With ANSI Escape in Console enabled the blue underlining for the stack trace hyperlinks no longer show up. You can still click on the text and it will take you to the spot in the code but new users do not know it is clickable because it is no longer blue or underlined like it is by default when ANSI Escape in Console is not enabled.
Is there a way to have the blue underlining still display properly via ANSI Escape in Console? I tried to add ANSI formatting around it but that breaks the hyperlink.
I'm using it since neon and it just essential. Log is really annoying to read it and it allow to glance at console.
With the latest version of eclipse (2019-03), I cannot change configuration for Ansi Console. In neon, a button at the right of disable/enable plugin opened configuration window. Do you know where is the configuration window ?
All of this combined with all platforms: Linux, Mac OS, and Windows
Did it on x64 platforms only, I don't have anything x32 anymore, sorry.
And it worked everywhere.
The enable / disable button is the same place as before, the top-right of the Console window, and I checked that it works.
I am quite sure I have no breaking changes, to it should (in theory) work all the way back to at least Neon (2016-06), but didn't test.
------------------------
"a button at the right of disable/enable plugin opened configuration window"
I never noticed this before. I do nothing in the plugin code to add such a button.
So I suspect that Eclipse was doing "some magic" to add it.
And maybe that "magic" was removed in 2019-something.
I have always accessed the configuration by going to Windows -- Preferences -- Ansi Console
I love the pluggin, works great, except for 1 small issue.
With ANSI Escape in Console enabled the blue underlining for the stack trace hyperlinks no longer show up. You can still click on the text and it will take you to the spot in the code but new users do not know it is clickable because it is no longer blue or underlined like it is by default when ANSI Escape in Console is not enabled.
Is there a way to have the blue underlining still display properly via ANSI Escape in Console? I tried to add ANSI formatting around it but that breaks the hyperlink.
Does not work properly with multiline coloring. I have about 30 lines of output from c++. Let's say the line 10 is the sequence of red color. Then 3 lines that should be red and the code for restoring the default color in the end of the third line. Other lines should have default color. With such output I've got red in different places while scrolling the eclipse's terminal. Sometimes red are first 10 lines, sometimes last part of the text. May be the plugin works only if setting and restoring sequences are localized in the same line?
It is a limitation in the Eclipse console itself: my plugin only get a line at the time, and when the console buffer gets full the top lines are dropped, the line numbers change, and all context is lost. So when coloring the current line there is no way to know what was set X lines above :-(
I am also anoyed by this bug, I have some idea. But is very hacky, but it might also mess up the performance.
Spring Boot applications that log using ANSI color codes won't display on the eclipse console. If the text is copied from the console to another app (say Terminal), you can read all the text. It is as though the text is rendered in the same color as the background color of the conole.
Hi, is it possible to turn on also ANSI-coloring during build in build console for ROS groovy projects?
For some reason it is not ANSI-colored here (Eclipse 4.4)
Sorry, I don't have an Ubuntu installed (just Win and Fedora).
I have found a VM, and I can try that.
But a quick look at the sources finds this "suspicious" line in catkin_make and catkin_prepare_release:
# force --no-color if stdout is non-interactive
if not sys.stdout.isatty():
args.no_color = True
Since Eclipse needs to capture its output, it starts the build with the stdio and stderr redirected.
And that makes sys.stdout.isatty() return False (because the Eclipse console is not really a terminal).
It looks like there is no way to get around this without code changes.
But you can just comment these two lines and it should work.
If you are on Windows, the terminal_color.py also needs some fixing, because it assumes that Windows cannot support ANSI escapes (not true):
if os.name in ['nt']:
disable_ANSI_colors()
The way I would fix ROS "for real" would be by adding a --force-color flag
(or do what most posix apps do: --color=never|always|auto and also honor an environment variable)
Anyway, if commenting the "if not sys.stdout.isatty():" does not work, please let me know, and I will go ahead and try top setup a working ROS environment.
Reviews Sign in to post reviews
works beautifully!
Submitted by Michał Szwejkowski on Tue, 2019-11-12 16:32
Nothing to add. Works marvelous. If you observe washed colors in Windows (against vivid in the Windows 10 command prompt) you can switch color palette in preferences. I observe xterm as closest to these in command prompt
No longer displaying the StackTrace hyperlinks in blue
Submitted by Scott Paskewitz on Mon, 2019-06-24 09:48
I love the pluggin, works great, except for 1 small issue.
With ANSI Escape in Console enabled the blue underlining for the stack trace hyperlinks no longer show up. You can still click on the text and it will take you to the spot in the code but new users do not know it is clickable because it is no longer blue or underlined like it is by default when ANSI Escape in Console is not enabled.
Is there a way to have the blue underlining still display properly via ANSI Escape in Console? I tried to add ANSI formatting around it but that breaks the hyperlink.
Essential but not working with latest version
Submitted by Alameda Lamelune on Wed, 2019-06-19 08:51
I'm using it since neon and it just essential. Log is really annoying to read it and it allow to glance at console.
With the latest version of eclipse (2019-03), I cannot change configuration for Ansi Console. In neon, a button at the right of disable/enable plugin opened configuration window. Do you know where is the configuration window ?
Re: Essential but not working with latest version
Submitted by Mihai Nita on Wed, 2019-08-28 16:02
Over the last few days I've tested it on:
All of this combined with all platforms: Linux, Mac OS, and Windows
Did it on x64 platforms only, I don't have anything x32 anymore, sorry.
And it worked everywhere.
The enable / disable button is the same place as before, the top-right of the Console window, and I checked that it works.
I am quite sure I have no breaking changes, to it should (in theory) work all the way back to at least Neon (2016-06), but didn't test.
------------------------
"a button at the right of disable/enable plugin opened configuration window"
I never noticed this before. I do nothing in the plugin code to add such a button.
So I suspect that Eclipse was doing "some magic" to add it.
And maybe that "magic" was removed in 2019-something.
I have always accessed the configuration by going to Windows -- Preferences -- Ansi Console
Thank you,
Mihai
Enormously Useful!!!
Submitted by Missing name Mising name on Sun, 2019-06-09 09:14
This plugin is enormously useful. I really think it should be installed by default in every new Eclipse release!
No longer displaying the StackTrace hyperlinks in blue
Submitted by Scott Paskewitz on Tue, 2019-04-09 12:22
I love the pluggin, works great, except for 1 small issue.
With ANSI Escape in Console enabled the blue underlining for the stack trace hyperlinks no longer show up. You can still click on the text and it will take you to the spot in the code but new users do not know it is clickable because it is no longer blue or underlined like it is by default when ANSI Escape in Console is not enabled.
Is there a way to have the blue underlining still display properly via ANSI Escape in Console? I tried to add ANSI formatting around it but that breaks the hyperlink.
Works great! Thanks for
Submitted by Christopher Wolf on Wed, 2019-02-20 16:57
Works great! Thanks for releasing and maintaining this!
Re: Works great! Thanks for
Submitted by Mihai Nita on Tue, 2019-02-26 13:21
Glad that you like it :-)
Mihai
Can't install on Eclipse 2018-12 (4.10.0)
Submitted by André Barranco on Mon, 2019-02-04 21:06
When I drag and drop the install button on my Workspace all I get is a blank (standard) Eclipse Marketplace window opened.
I know it omits 4.10 support, but I know the Spring Tool Suite based on Eclipse 4.10 has it, so I thought I'd manage to get it working.
Re: Can't install on Eclipse 2018-12 (4.10.0)
Submitted by Mihai Nita on Thu, 2019-03-07 04:51
Unfortunately it does not always happen, is pretty rare, so it is hard to debug :-(
Can you please give it another try? I have uipdated the URL, making sure it does not end up in a redirect.
And I made sure to set the falg that Eclipse 4.10 is supported (it worked without changes, it was only a setting in the Marketplace)
Sorry for the troubles,
Mihai
Sweet!
Submitted by Arno Unkrig on Thu, 2019-01-10 04:29
Now the logging of my SPRING BOOT application is no longer scrambled with ANSI control characters. Exactly what I wanted.
The plugin appears to modify the standard console view, instead of adding a new view. No need to (re)configure anything.
Site not reached
Submitted by Daniel Robinson on Mon, 2018-10-01 19:51
I get this error:
Unable to read repository at http /www.miha i-nita.net/ eclipse/content.xml.
Received fatal alert: internal_error
Eclipse IDE for C/C++ Developers, with WICED SDK 3.4.0
Version: Luna Service Release 2 (4.4.2)
Build id: 20150219-0600
Re: Site not reached
Submitted by Daniel Robinson on Tue, 2018-10-02 10:39
I switched to a different version of Eclipse and was able to install from the Marketplace to that version's plugins directory.
I copied the JAR file to the plugins directory of the version that failed to load and it works.
There appears to be a version incompatibility between the version of Eclipse used by Cypress and the Marketplace (at least for this package.)
Multiline coloring doesn't work properly
Submitted by Andrey Solovjev on Sun, 2018-08-05 05:05
Does not work properly with multiline coloring. I have about 30 lines of output from c++. Let's say the line 10 is the sequence of red color. Then 3 lines that should be red and the code for restoring the default color in the end of the third line. Other lines should have default color. With such output I've got red in different places while scrolling the eclipse's terminal. Sometimes red are first 10 lines, sometimes last part of the text. May be the plugin works only if setting and restoring sequences are localized in the same line?
Oxygen.3a Release (4.7.3a)
Re: Multiline coloring doesn't work properly
Submitted by Mihai Nita on Fri, 2018-08-10 18:20
Unfortiunately, a known problem, and one that I don't really think I can solve.
https://github.com/mihnita/ansi-econsole/issues/3
It is a limitation in the Eclipse console itself: my plugin only get a line at the time, and when the console buffer gets full the top lines are dropped, the line numbers change, and all context is lost. So when coloring the current line there is no way to know what was set X lines above :-(
I am also anoyed by this bug, I have some idea. But is very hacky, but it might also mess up the performance.
Sorry,
Mihai
does not work in Mac OS High Sierra
Submitted by Sepideh Asadi on Fri, 2017-10-20 08:45
Could you notify us whenever you have a new release of "ANSI Escape in Console" for Mac OS High Sierra?
I am using Eclipse C++ in Mac OS High Sierra. It seems this pluging removed a part of messages in the console.
s_asadi83[at]yahoo.con
Won't render ANSI color text on Mac OS High Sierra (Public Beta)
Submitted by Rory Carr on Thu, 2017-07-06 17:48
Spring Boot applications that log using ANSI color codes won't display on the eclipse console. If the text is copied from the console to another app (say Terminal), you can read all the text. It is as though the text is rendered in the same color as the background color of the conole.
Re: Won't render ANSI color text on Mac OS High Sierra
Submitted by Mihai Nita on Tue, 2019-02-26 13:24
Works now.
This looked like a system / SWT problem. Fixed meantime (by Mac OS or Eclipse, I don't know)
Re: Won't render ANSI color text on Mac OS High Sierra
Submitted by Mihai Nita on Tue, 2017-10-03 02:28
This seems to be a system / SWT problem.
Bug opened, https://bugs.eclipse.org/bugs/show_bug.cgi?id=525383
Re: Won't render ANSI color text on Mac OS High Sierra
Submitted by Atlas Amfistomos on Wed, 2017-09-27 09:26
Still occurs with Mac OS High Sierra official release...
Re: Re: Won't render ANSI color text on Mac OS High Sierra
Submitted by Mihai Nita on Tue, 2017-10-03 02:29
This seems to be a system / SWT problem.
Bug opened, https://bugs.eclipse.org/bugs/show_bug.cgi?id=525383
Cannot Install
Submitted by Himadri Sengupta on Tue, 2016-12-13 05:07
Cannot Install. Facing error
"Unable to read repository at http-www mihai-nita net -eclipse-content xml
peer not authenticated"
Can anyone look into this Please..
ANSI-coloring during build ROS groovy projects?
Submitted by Valery Mising name on Fri, 2014-09-26 06:32
Hi, is it possible to turn on also ANSI-coloring during build in build console for ROS groovy projects?
For some reason it is not ANSI-colored here (Eclipse 4.4)
ANSI-coloring during build ROS groovy projects?
Submitted by Mihai Nita on Tue, 2014-09-30 23:59
Sorry, I don't have an Ubuntu installed (just Win and Fedora).
I have found a VM, and I can try that.
But a quick look at the sources finds this "suspicious" line in catkin_make and catkin_prepare_release:
# force --no-color if stdout is non-interactive
if not sys.stdout.isatty():
args.no_color = True
Since Eclipse needs to capture its output, it starts the build with the stdio and stderr redirected.
And that makes sys.stdout.isatty() return False (because the Eclipse console is not really a terminal).
It looks like there is no way to get around this without code changes.
But you can just comment these two lines and it should work.
If you are on Windows, the terminal_color.py also needs some fixing, because it assumes that Windows cannot support ANSI escapes (not true):
if os.name in ['nt']:
disable_ANSI_colors()
The way I would fix ROS "for real" would be by adding a --force-color flag
(or do what most posix apps do: --color=never|always|auto and also honor an environment variable)
Anyway, if commenting the "if not sys.stdout.isatty():" does not work, please let me know, and I will go ahead and try top setup a working ROS environment.
Thank you,
Mihai
ANSI-coloring during build ROS groovy projects?
Submitted by Mihai Nita on Mon, 2014-09-29 13:35
I don't know, I have never played with ROS. Let me give it a try, and will get back to you.
Thank you!
Mihai
Colorize your CLI
Submitted by Paul Verest on Tue, 2014-04-01 10:49
Just look at picture and try to recall all those ANSI codes...