<dnkl>
WhyNotHugo: besides quitting the shell or whatever application you're running in the terminal? Nothing that comes to mind...
<dnkl>
maybe OSC-52 (clipboard access)
h-erectus has quit [Ping timeout: 240 seconds]
h-erectus has joined #foot
emcconville has quit [Ping timeout: 252 seconds]
<armin>
dnkl: there's this one feature i keep "kitty" installed for: "kitty list-fonts". is there something like this in foot?
<dnkl>
what exactly does it do?
emcconville has joined #foot
<armin>
dnkl: it lists installed fonts in a terminal, nothing special, just shows a nicely formatted list of, uhm, font-names!
<armin>
dnkl: i've never found another way to do exactly that, i believe?
<dnkl>
just use fc-list?
emcconville has quit [Client Quit]
emcconville has joined #foot
<armin>
dnkl: that's a bit chaotic compared to the "kitty list-fonts" output (which is grouped by the parent font or something, shown in green, and without the full path name of the .ttf file)
<armin>
but yup, works.
<armin>
hm, doesn't output the font name in exactly the syntax i can use in foot.ini
<dnkl>
should be possible to either format there output with fc-list options, or cut/sed/awk the output a bit (and maybe wrap it in a script)
<armin>
ah it does!
<dnkl>
yes, output is usable as-is in foot.ini (minus path to font file, obviously)
emcconville has quit [Client Quit]
emcconville has joined #foot
<dnkl>
there's also an undocumented --format option to fc-list
<dnkl>
"fc-list | cut -d ':' -f 2- | sort | uniq" is pretty close to a "nicely formatted" list ;)
<armin>
ultraskeuomorphism3d, that was the "future" back then.
<cc0>
hehe somehow i hoped that this command would display each line in its own font
<armin>
cc0: there are some graphical applications that do this, but i believe that's not possible from a terminal.
<dnkl>
armin: cc0: hb-view has sixel support...
<dnkl>
as to whether drop shadows makes sense... I guess there are people who'd like it, but most don't.
<dnkl>
in any case, it's not something foot will support
<dnkl>
re hb-view and sixel: more precisely, they can optionally use chafa. They appear to use the library, not exec:ing the chafa binary (so needs to be built against libchafa)