Open acook opened 2 years ago
xterm-256color
definitely works for me in both macOS (with iTerm and Terminal.app) and Linux using the various terminal emulators I have installed.
Can you tell me a bit more about which operating system and terminal you're using?
Oops, sorry, I misread the original post. Hmm, I'm not sure why it wouldn't support screen-256color
-- I'll have to play around a bit with it... but like I mentioned in the previous post, the app relies on ncurses
for color mode capabilities detection.
Yeah it's weird, it's the only app I've used with this problem. It could be that my other terminal apps are forced to true color, or don't check? I'm not sure. If you can think of something that would give me similar results, or something I can run to extract what ncurses is telling musikcube
I'll do that to help figure it out.
I'm on Solus Linux, fully updated. It ships with Gnome Terminal:
Linux monolith 5.14.21-210.current #1 SMP PREEMPT Sun Dec 5 21:23:09 UTC 2021 x86_64 GNU/Linux
Version 3.42.1 for GNOME 41
A terminal emulator for the GNOME desktop
Using VTE version 0.64.2 +BIDI +GNUTLS +ICU +SYSTEMD
Hey, thanks for the great program!
Just to say that on my home server - where I do not run X there is no possibility to change the colour scheme. I mean the terminal is the real terminal. Is it supposed to be like that or am I missing something?
Thanks R
When using
screen-256color
musikcube
launches successfully but falls back to a default color scheme (instead of my custom true color scheme) but works fine withTERM=xterm-256color musikcube
.When I pass in, say,
TERM=foobar musikcube
, it fails to set up a terminal with:The above error seems to be similar to the output of
tput
, buttput
outputs 256 for bothxterm-256color
andscreen-256color
.I dug around in the code a little trying to understand where
musikcube
was getting its info but other thanColors.cpp
I wasn't sure.