Gnome 3.8 removed transparency and some other features from gnome-terminal. I was going to post a link to the bugzilla report - but it's getting an internal error / not working. Regardless, it's _even_ on wikipedia (lulz); http://en.wikipedia.org/wiki/GNOME_Terminal#Background
..But maybe you are using Ubuntu (or another distro patching it) and just aren't aware of the situation. [Ubuntu /possibly others are patching patching 'post-3.8 releases' of gnome-terminal [so am i]. (Ubuntu gnome-terminal-3.8.0 change log); https://launchpad.net/~gnome3-team/+...-archive-extraOriginally Posted by wikipedia
* note the 02_add_transparency_properties.patch under 'debian/patches'.
Still a lot of performance issues.
Which is realted to: https://mail.gnome.org/archives/clut.../msg00010.html
Taken from http://blog.finalterm.org/2013/09/becoming-big.htmlPerformance Breakthrough
Many of the "improvements" made in the past months have slowed down Final Term, and two weeks ago, it at last became clear to me that development of terminal functionality could not continue in earnest without fixing the performance first.
As a result, a number of changes were made to bring Final Term up to speed. It is now "only" 8-10 times slower than GNOME Terminal, which isn't anything to write home about but might be excused given that Final Term manages a much more complex model of the terminal output. In practice, the difference should be hardly noticeable.
Once the remaining problem, absurdly high CPU usage when idle, is fixed (which you can help with by answering https://mail.gnome.org/archives/clut.../msg00010.html!), Final Term's performance will be ready for the initial release.
It's nice that it's available but I'd rather Gnome adopt Final Term (http://finalterm.org/). It's nowhere near ready yet (doesn't handle output properly for even something like top, and uses too much memory/cpu) but it has such a good start. Its borrowed features from fish, hotwire, and probably others. That is what a nextgen terminal should look like.
They say, that the feature was removed in a restructuration process of the old code base, in order to raise the code quality. Some memory leaks could be fixed that way. Maybe it will return in the future. I'm wondering if this transparency was portable to wayland, anyway. But I couldn't care less, as I préfère a solid background - makes the output way better readable for me than anything transparent.
How can anyone use a transparent terminal?
If the clean up of the code base resulted in the rewrap functionality the loss of transparency was a good sacrifice.
Last edited by Akka; 12-10-2013 at 07:19 PM.