Community
Participate
Working Groups
At the moment errors from decoding escape sequences are silently discarded if full logging is not turned on. As there is a performance impact of full logging* this bug is to try to find the middle ground that allows users to identify and report back cases where escape sequences are not handled by the VT100Emulator
Gerrit change https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179701 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=b7d017572d007bd1bc7e8564b6248229901b41ca
Gerrit change https://git.eclipse.org/r/c/cdt/org.eclipse.cdt/+/179702 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=4ef3cb7f303659fe4c1311cff7b419d7f0b91198
This takes on more importance with ConPTY - Since ConPTY generates its own stream of escape sequences, we need to know what they are, so having better error reporting is an increased priority. I don't see any documentation of what escape sequences ConPTY can generate, although I have already fixed Bug 573713 which was one example of that.
(Sorry - Covid summer used up too much of my time and these items did not make it into CDT 10.4. Retargetting for 10.5)
I am working on this in the background - but not sure which version of CDT I will get this resolved in.