|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #57658] grey text color after error message in gui console |
Date: | Fri, 24 Jan 2020 03:55:32 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36 |
Update of bug #57658 (project octave): Status: Confirmed => Need Info _______________________________________________________ Follow-up Comment #6: Very impressive ^^ My idea is that gcc is tampering with the terminal colors since recent versions. For Octave 5.1.90: >> system ("gcc -v") [...] gcc version 9.2.0 (GCC) For Octave 5.1.90: >> system ("gcc -v") [...] gcc version 7.4.0 (GCC) To get some sort of "normal" colors back, one can use system ("COLOR 01") or has to restart the Octave session. Maybe there is a smarter command to reset the window colors? Please share. To totally avoid this tampering, if I compile with mkoctfile -fdiagnostics-color=never ....... https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/Diagnostic-Message-Formatting-Options.html Then it looks pretty much "colorless" as in Octave 5.1.0. Thus an emergency change would be to add "-fdiagnostics-color=never" to the standard options of mkoctfile. Thoughts? _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57658> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |