-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support True Colors in Terminal #772
Comments
I found a way around this. In Guake, echo your By the way, what DE are you running? |
I cannot get it to work properly , does guake support true colors ? or is it approximations based on the terminal color palette ? His IDE seems to be neovim btw :) |
My TERM variable is set to screen-256color (in tmux at least) and xterm-256color outside of it, but that doesn't change anything. The editor in the screenshots is indeed NeoVim. |
@Happykat I was asking what his desktop environment was, not his integrated development environment 😜 @FujiMakoto Here's a Perl script which will test things for you. Run this script and you'll be able to see the full spectrum of what is supported. This isn't my script. I'm not sure if Guake supports true colors, but I'm running tmux and I'm getting pretty good color support: If you run that script in a terminal emulator that you know has true color support, just screenshot and compare the results. |
Ah, you are testing _256color_ support, not true color (16 million colors) support. Use the awk script posted here to check for true color support, Here is a comparison of the script run in Gnome Terminal and Guake, Also, the DE is Unity with the Numix theme, sorry about that. He made me see an I that wasn't there 😛 |
@rfkrocktk Oh sorry >< i read IDE my bad >< @FujiMakoto i have made it one step further , but still it is NOT true color support : You can see that it is not smooth at all... I am using guake , with tmux . echo $TERM report : screen-256color my zshrc , init.vim and tmux.conf are on my Dotfile repo. I don't see how to activate true color support. @FujiMakoto What version of guake are you using btw ? |
@Happykat: 0.8.5.1 (0.8.5-1 |
not not sure vte support true color |
Gnome Terminal is VTE with true color support, for what it's worth. |
yes, but should be a new version of vte. With gtk2, we are stuck with an old version (e: does not provide search method, while gtk3's ate provides it, and so on) |
Is there any plan to port to gtk3 soon ? |
Rewrite started. Might be finished until end of this year... Le vendredi 29 juillet 2016, Hector [email protected] a écrit :
Gaetan |
Okay , great news ! Thanks for the quick reply ! |
This could be relevant: |
Waiting till finished. Tilda has this already. Using tilda for the time being :) |
Any progress with this? |
I'm also interested in this, our terminals would be much better. Hopefully a new version of guake with true color support soon. Thanks. |
Guake supports true color now correct? |
Can someone test on Guake 3 ? I guess VTE now allows this, but I may have to tune the environment variables |
great:) |
Great! Any ppa for ubuntu? |
@AnwarShah Only for bionic. But you can get the latest Guake by running:
|
Thank you. I've installed from the source repo |
It is risky to install like this. At least use --user. Avoid as much as possible to install any python package using sudo pip3. |
I installed using `make` and `make install`. Didn't use pip
…On Sun, Feb 18, 2018 at 9:34 PM, Gaetan Semet ***@***.***> wrote:
It is risky to install like this. At least use --user. Avoid as much as
possible to install any python package using sudo pip3.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#772 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABzG1S-Q7hLrsffeBtyhw4217csHjgtoks5tWEMHgaJpZM4JLtDT>
.
|
Many other terminals support true 24-bit color including
pantheon-terminal
and the terminal shipped in Atom'sterminal-plus
package. Guake's terminal doesn't seem to provide this as demonstrated in the screenshot.The text was updated successfully, but these errors were encountered: