<barusu>
Regarding dynamically changing the terminal colors, I noticed that only terminals running the shell are reloaded.
<barusu>
If I have a TUI app running in a terminal, then that terminal does not reload the colors because it does not have the shell running in the background.
<barusu>
Is there a way I can tell foot to reload it's colorscheme?
<barusu>
Does it make sense to send the sequences to every pts file under /dev/pts/?
<dnkl>
broadcasting to /dev/pts is the only supported way of changing colors on all running terminals. We will not add support for config reload.
<barusu>
That makes sense. It's functionally equivalent
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
<barusu>
dnkl: I think there might have been a misunderstanding, the patch I submitted way back was to allow changing alpha using a keymap.
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
hmht has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
erectus has quit [Remote host closed the connection]
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
erectus has joined #foot
boomboxnation has quit [Read error: Connection reset by peer]
boomboxnation has joined #foot
<baltazar>
also note that I also have a PR implementing the same functionality, but mine also has a keybind for toggling alpha: https://codeberg.org/dnkl/foot/pulls/1143 (I've been building my own foot with this pr applied ever since I created it)
an3223 has quit [Remote host closed the connection]
an3223 has joined #foot
<anarcat>
dnkl: it seems the gnome folks got some custom hardware going
<anarcat>
it's a little involved, but doesn't seem to bonkers for someone who's ever messed with a micro-controller