Closed nicos68 closed 1 year ago
Ok so it looks like if I run tmux new-session -As "tmux"
straight from my shell prompt it works as expected, but if I run it from a script file it reproduces the issue.
Would anyone have any advice ? Even though I concede that this looks more like an alacritty/tmux issue
The -A flag makes new-session behave like attach-session if session-name already exists
Can you confirm if your bug is reintroduced if you run tmux new-session -s "tmux"
?
Perhaps it has something to do with the attach mechanism.
The -A flag makes new-session behave like attach-session if session-name already exists
Can you confirm if your bug is reintroduced if you run
tmux new-session -s "tmux"
?Perhaps it has something to do with the attach mechanism.
No, if I just remove the -A
option the issue is not reproduced.
I just made a test with kitty and the colors look right, even when using t
. So it looks like an alacritty issue :/ If you're curious you can have a look at my alacritty config here
Alacritty recommends you set the TERM variable directly on your Alacritty config.
env:
TERM: xterm-256color
@nicos68 let me know if you're still seeing this issue.
Alacritty recommends you set the TERM variable directly on your Alacritty config.
env: TERM: xterm-256color
Thanks, that does fix the issue (after restarting alacritty, which may not be obvious).
If I open tmux using the
tmux
command, the status background color corresponds to what I setup in my config : However, if I uset myproject
to open a new session, my settings are ignored: Also in this case, my nvim background color is wrong : whereas in the first case it is correct :I set up a minimal reproducible example here : https://codeberg.org/nise/dotfiles/src/branch/t-color-issue/.config/tmux/tmux.conf