cbb has quit [Read error: Connection reset by peer]
lanodan has joined #foot
radu2427530 has joined #foot
radu242753 has quit [Ping timeout: 260 seconds]
radu2427530 is now known as radu242753
radu2427532 has joined #foot
radu242753 has quit [Ping timeout: 256 seconds]
radu2427532 is now known as radu242753
lechner has quit [Ping timeout: 240 seconds]
lechner has joined #foot
lechner has quit [Remote host closed the connection]
lechner has joined #foot
lechner has quit [Ping timeout: 256 seconds]
radu2427531 has joined #foot
radu242753 has quit [Ping timeout: 240 seconds]
radu2427531 is now known as radu242753
lechner has joined #foot
Nulo has quit [Ping timeout: 260 seconds]
Nulo has joined #foot
radu2427530 has joined #foot
radu242753 has quit [Ping timeout: 256 seconds]
radu2427530 is now known as radu242753
bgs has quit [Remote host closed the connection]
caveman has quit [Remote host closed the connection]
cvmn has joined #foot
radu2427538 has joined #foot
radu242753 has quit [Ping timeout: 240 seconds]
radu2427538 is now known as radu242753
anarcat has quit [Read error: Connection reset by peer]
anarcat has joined #foot
cbb has joined #foot
xd1le has joined #foot
<xd1le>
I have this issue, but I'm not sure if it is expected behaviour or what..
<xd1le>
I'm using emacs (28) with true color support and it's working, except that it seems that the black color (#000000) is actually displayed as grey
<xd1le>
but all other colors seems to display properly
<xd1le>
Anyway, I'm confused, shouldn't the display of #000000 be independent of the terminal color theme? (with truecolor)
<xd1le>
To clarify, that person on stackexchange was not using truecolor, so I understand why the fix for them was changing their terminal color theme.
<xd1le>
my foot is foot version: 1.13.1 -pgo +ime -graphemes -assertions
<dnkl>
xd1le: never noticed it before, but you're right. No idea why, but can only guess that Emacs chooses to do this.
<xd1le>
hmm ok, but I checked on alacritty as well and over there with M-x display-colors the #000000 displays as black
<xd1le>
sorry I should have mentioned that too
<dnkl>
not for me; it's brown for me in Alacritty
<dnkl>
i suspect emacs falls back to indexed colors for at least #000000-#000007.
<dnkl>
echo -e '\e[30m test \e[m' results in the same color as Emacs' #000000, as far as I can tell
<dnkl>
yup, that's it. setting colors.0=ff0000 in foot results in emacs' #000000 bring red
<dnkl>
being*
<xd1le>
hmm ok
<xd1le>
is \e[30m the terminal color 0?
<dnkl>
yes "regular0"
<dnkl>
or index 0 in the 256 palette
<dnkl>
same thing
<xd1le>
"I suspect..." <-- yes I figured something like this but still wasn't sure
<xd1le>
intersting
<dnkl>
they hint at this in the emacs docs
<xd1le>
this is really annoying
<dnkl>
"colors-on-a-tty"
<xd1le>
yes I remember, thanks
<xd1le>
ty dnkl for checking this
<xd1le>
so in the manual it mentions "Terminals with ‘RGB’ capability treat pixels #000001 - #000007 [...]"
<xd1le>
but I guess it is doing it for #000000 too
<dnkl>
yes, I noticed that too, but yeah, they obviously do it for #000000 as well
<xd1le>
this is really annoying espcially if I want to use a light background foot theme, but I want to use true black for #000 in emacs
<xd1le>
Do you think it would work if I set color0 to #000000 in foot, but change background to another color with OSC ?
<xd1le>
if that makes sense
<dnkl>
a perhaps better solution is to create a new terminfo, where setaf/setab only uses the 24-bit escapes.
smach has joined #foot
<xd1le>
alright ty
radu2427539 has joined #foot
radu242753 has quit [Ping timeout: 260 seconds]
radu2427539 is now known as radu242753
<xd1le>
hmm, if you have time, how do I do that?
<xd1le>
or, where can I find out how to read the setab and setaf definitions
<xd1le>
ah I see the terminfo manpage explains the % encodings
<cbb>
dnkl: xd1le: the xterm+direct terminfo fragment has a comment about that issue
<xd1le>
it has the line: "If Terminfo database is not available, but 24-bit direct color mode is supported, it can still be enabled by defining the environment variable COLORTERM to 'truecolor'.
<cbb>
tbh I'm not too sure about emacs specifically
<cbb>
I just recognize that issue regarding #000000-#000007 from previous encounters with it
<cbb>
it's usually down to using terminfo, but I could be wrong in this case
<xd1le>
well I guess emacs is using it, and just that line means to override the check and enable 24-bit color anyway
<xd1le>
but yeah it's strange that it's still using #000000-#000007 from color map
<xd1le>
like I thought it would be foot doing that, not emacs
<cbb>
the paragraph at the very bottom of that page seems relevant
<xd1le>
but yeah it is emacs because same thing happens with alacritty
<cbb>
it's talking about "setb24" and "setf24" capabilities
<cbb>
the foot terminfo doesn't have those
<cbb>
I think they're very much emacs-specific
<cbb>
some other apps use "setrgbb" and "setrgbf" for a similar purpose
<xd1le>
I see
<xd1le>
so you think if I just have a line like "setb24, setf24,"?
<xd1le>
I guess I'll just try
<cbb>
that page isn't specific enough about how it all works
<cbb>
and whether or not $COLORTERM or that last paragraph takes precedence
<cbb>
they're making it way harder than it needs to be though
<cbb>
it's kind of a complex issue and really hard to simply summarize
<cbb>
I don't use emacs though, so I can't give you any insight about the specifics
<xd1le>
ok well, I just tried it with a "setb24, setf24," line below the setaf line, with tic command
<xd1le>
and it doesn't seem to work
<xd1le>
(and without $COLORTERM and with that custom terminfo it also does not work)
<xd1le>
ah well
<cbb>
$COLORTERM is just a way to "detect" that the terminal supports 24-bit colors
<cbb>
it doesn't actually specify which escape sequences to use
<xd1le>
yeah, I just tried it because you mentioned about $COLORTERM vs setb24 and setf24 precedence
<xd1le>
just in case
<xd1le>
yeah I don't understand.. if emacs is using terminfo, then how can it still use 24-bit color "if terminfo database is not available"
<cbb>
if I had to guess, I'd say it probably uses hardcoded terminfo strings
<cbb>
since that'd be the simplest stand-in, if it normally uses terminfo
<xd1le>
ah yeah
<xd1le>
good point
<cbb>
that just goes to show how pointless using terminfo is though
<cbb>
that it's not even needed and can be replaced with hard-coded strings
<cbb>
because literally every terminal that supports 24-bit colors uses identical escape sequences
<xd1le>
yeah I was just thinking that actually
<cbb>
in a sane world, it'd detect support for it (e.g. from $COLORTERM) and then just emit the standard escape sequences
<cbb>
the complexity in those docs is absolutely insane tbh
<cbb>
and entirely self-inflicted
<cbb>
I guess the only way to tell what it's actually doing is to look at the source code
<xd1le>
yeah I guess for setb24 and setf24, I'd have to construct an implementation somehow. I wish emacs would have just told me what to use.
<xd1le>
yeah I think I'll just stick to the hacky workaround using OSC
<xd1le>
I think I tested it few hours ago and it should work
<xd1le>
and I can just use [environment] field in foot.ini to be able to access the color I really wanted for the background (in the shell)
<xd1le>
if it was only #000001-#000007 I think it wouldn't be that big of a deal. But #000000 is used in a lot of themes
<cbb>
color 16 in the 256-color palette is #000000 by default
smach has quit [Read error: Connection reset by peer]
Nulo has quit [Ping timeout: 260 seconds]
Nulo has joined #foot
cbb has quit [Quit: WeeChat 3.7.1]
sentriz has quit [Remote host closed the connection]
sentriz has joined #foot
<anarcat>
hello, me again :)
<anarcat>
i start a lot of terminals in my day... every time i do so, foot dumps about 20 lines in my logs
<anarcat>
mostly about... well, not really important stuff :)
<anarcat>
can we turn that stuff off?
<anarcat>
oh, i see there's a log-level option on the commandline, but is there a config file option?
<anarcat>
foot.ini(5) doesn't think so
<anarcat>
oh i see the discussion
<anarcat>
sigh
<anarcat>
well it would sure be nice to have a cleaner default anyways, and it's not really an option for me to override the commandline everywhere i call foot
<baltazar>
anarcat: fwiw I just have $TERMINAL set to `foot -dwarning` and use that wherever I start a terminal, e.g. in my sway config I have `bindsym $mod+Return exec "$TERMINAL"`
ayushnix has quit [Remote host closed the connection]
bgs has quit [Remote host closed the connection]
smach has joined #foot
smach has quit [Quit: No Ping reply in 180 seconds.]