Closed alexanderjeurissen closed 7 years ago
alexanderjeurissen
commented
7 years ago This probably has to do something with how true color is emulated in tmux. I remember having to put in some work getting it to work on my work machine, probably forgot to also do this on my home machine.
I tested with tmux info | grep Tc and got TC[missing] so something is wrong. I'll investigate my configuration and if this turns out to be a gotham issue I'll reopen.
alexanderjeurissen
commented
7 years ago Quick update: turned out to be a quirk in my tmux configuration. following diff fixed it:
diff --git a/tmux.conf b/tmux.conf
index 93b850e..7a49037 100644
--- a/tmux.conf
+++ b/tmux.conf
@@ -16,8 +16,7 @@ set -g default-command "reattach-to-user-namespace -l zsh" # fix terminal-notifi
# Enable true (24bit) colors for version >= 2.2
# See https://deductivelabs.com/en/2016/03/using-true-color-vim-tmux/
-set -ga terminal-overrides ",xterm-256color:Tc"
-
+set -ga terminal-overrides ',*:Tc'
set -g base-index 1 # start with window 1 (instead of 0)
set -g pane-base-index 1 # start with pane 1
Something ain't right with the way colors are rendered when neovim is using termguicolors and is running inside a tmux session:
Tmux session + neovim + termguicolors:
Neovim + termguicolors:
I'm not really sure what is causing the unexpected behaviour. term is correctly set to
screen-256colortermguicolors is enabled in both instancesWhen I disable termguicolors whilst in tmux then the colors do render better but termguicolors should work in tmux sessions as I can successfully use other colorschemes that way.