From b73bf53bd30cb8b6056888a473368968041dbe66 Mon Sep 17 00:00:00 2001 From: Fabian Homborg Date: Tue, 20 Oct 2015 17:02:32 +0200 Subject: [PATCH] Enable 24-bit mode for selected terminals Unfortunately, there's no standard way to detect support (importantly, terminfo doesn't encode it), but there's a variety of terminals that support it that we can detect. It's better than letting this functionality go to waste. Check KONSOLE_PROFILE_NAME instead of DBUS_SESSION because Konsole can be compiled without dbus support. Check ITERM_SESSION_ID's format for 24bit support This has changed since the last release, just like 24bit support. So if we check one, we get the other. --- share/functions/__fish_config_interactive.fish | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/share/functions/__fish_config_interactive.fish b/share/functions/__fish_config_interactive.fish index 2f1705228..23c60195f 100644 --- a/share/functions/__fish_config_interactive.fish +++ b/share/functions/__fish_config_interactive.fish @@ -320,4 +320,13 @@ function __fish_config_interactive -d "Initializations that should be performed fish_fallback_prompt end end + + if begin set -q KONSOLE_PROFILE_NAME # KDE's konsole + or string match -q -- "*:*" $ITERM_SESSION_ID # Supporting versions of iTerm2 will include a colon here + or string match -q -- "st-*" $TERM # suckless' st + or test "$VTE_VERSION" -ge 3600 # Should be all gtk3-vte-based terms after version 3.6.0.0 + or test "$COLORTERM" = truecolor -o "$COLORTERM" = 24bit # slang expects this + end + set -g fish_term24bit 1 + end end