ANSI Escape in Console

It might be this:
https://github.com/mihnita/ansi-econsole/issues/27

Meantime I've put a lot of work on performance, and at this point the performance with the plugin uninstalled / disabled / enabled are very similar, for both light / dark themes.

Trouble is, Eclipse is slow, and is getting worse.

With 2020-09 the performance of Light mode got as slow as the Dark one.
Eclipse 2020-12 adds a new Console setting, "word wrap",  more than 20 times slower for some use cases (like the code from youngm, Dec 2018).

I've added some checks and if the Console settings are known to be performance bottlenecks I warn, and explain where to change them.
I don't have the right to change them myself, as they don't belong to my plugin.

But increassing the buffer size helps (Preferences -- Run/Debug -- Console -- Limit console outpout).
Using 1 million feels a lot better (the default is 80K)

Console hang issue and slow performance on Windows
https://github.com/mihnita/ansi-econsole/issues/66

I've answered Christopher by email.

But the gist was: I don't think it is possible to implement the complete set of ANSI commands on top of the existing Eclipse Console.
Maybe a couple of things like erase from begin / to end of line / document. Character positioning and changing there would probably be too messy.

But it might be possible to take the TM terminal plugin and either replace the default console with it, or have a way to run applications run in it.

https://github.com/mihnita/ansi-econsole/issues/32

And I think I have some way to fix that...

Fiexd!!! A bit messy, but worth it :-)

Cheers,
Mihai

Over the last few days I've tested it on:

• Eclipse 4.12 (2019-06)
• Eclipse 4.11 (2019-03)
• Eclipse 4.10 (2018-12)
• Eclipse 4.9 (2018-09)
• Eclipse 4.8 (Photon)

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

Did you manage to solve this?

I've tested the latest version from mars (2015) to latest Eclipse.
Did it on Linux (2 distros), Win 10, and Mac OS.

Should be fine.

There is a small bug where the icon is enabled when you start Eclipse even if in fact the plugin is disabled.
But the status is actually preserved, it starts the way it was when exiting Eclipse. It is just the indicator that is wrong.
I have a bug opened for it, and I'm trying to solve it, because I find it anoying too (even if I almost never disable the plugin :-).

Regards,
Mihai

Fixed!!! (Jan 2020 :-)

Glad that you like it :-)

Mihai

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

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.)

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

Still occurs with Mac OS High Sierra official release...

This seems to be a system / SWT problem.
Bug opened, https://bugs.eclipse.org/bugs/show_bug.cgi?id=525383

Works now.
This looked like a system / SWT problem. Fixed meantime (by Mac OS or Eclipse, I don't know)

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

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