Closed ngocphamm closed 3 years ago
Thanks for taking the time to report this in so much detail.
It looks like the issue in your case if that $TERM
is set to screen-256color
which will have ticker fallback to ANSI256 colors. The logic for this fallback is defined in a dependency of ticker here if you're interested in having a look.
You can try starting ticker with the $TERM value set for this one command e.g. TERM=truecolor ticker -w AAPL
Hope that helps
Thanks @achannarasappa for your response! I just wanted to know which one is supposed to be the correct truecolor supported by ticker and from your answer, it's the first screenshot (without tmux). I got that by changing the $TERM
to tmux-256
with a patch for macOS, so it's all good now.
Thank you for making this!
Describe the bug I really don't know if this is a bug, and I think it's not likely. I just noticed some small differences in colors when using
ticker
inside tmux, and I'm not sure what's supposed to be the "correct" one.To Reproduce Steps to reproduce the behavior:
ticker
in an iTerm2 sessionticker
in another iTerm2 session, with tmuxScreenshots Without tmux
With tmux
Environment (please complete the following information):
Additional context I think both iTerm2 itself, and tmux support True Color, and just that the 2 report a different
$TERM
(see the lower parts of the 2 screenshot).iTerm2 ->
$TERM = xterm-256color
tmux ->$TERM = screen-256color
. This is due tonvim
's:checkhealth
complaining about the$TERM
should bescreen-256color
.config/ticker.yaml
- made up numbers