dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.15.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
rcf has quit [*.net *.split]
ewb has quit [*.net *.split]
alexander has quit [*.net *.split]
rcf has joined #foot
alexander has joined #foot
fraolt_ has quit [Ping timeout: 240 seconds]
fraolt_ has joined #foot
rcf has quit [Quit: WeeChat 3.8]
rcf has joined #foot
lack has quit [Read error: Connection reset by peer]
lack has joined #foot
<dnkl> nmschulte: foot itself never creates or writes to ~/.config/foot/foot.ini.
<dnkl> sewn: :)
<nmschulte> Yeah I'm very uncertain wtf happened. the file had creation and mod time of ... today, and I'm 99.99999% sure I had one there, like 100% sure.
<nmschulte> It didn't occur on my other system w/ similar setup.
bgs has joined #foot
bgs has quit [Remote host closed the connection]
<nmschulte> so it says .config/foot/ was modified today, and that .config/foot/foot.ini was created and modified today.
<nmschulte> I am kind of worried about how this would have happened.
<nmschulte> .bash_history even shows only two histories touching .config/foot/: last year when I did, and today when I started investigating.
<nmschulte> Maybe install the old package ver and revert my changes and see how foot behaves?
<dnkl> nmschulte: guess it's possible the new package had some kind of upgrade/migration script?
<dnkl> sewn: btw, remember that subpixel antialiasing won't work with transparent backgrounds
<sewn> does that have a fix? i dont actually check for transparent stuff when doing fcft text rendering, but it does use a regular pixman_color_t color
<dnkl> not that I'm aware of. Subpixel antialiasing uses the individual RGB colors of a pixel to increase the horizontal resolution of the antialiasing. How can you get the correct color when the background is transparent and you don't know the background color?
<dnkl> anyway, fcft can't help you, since it only has access to the source glyph. Not the destination buffer
<Arnavion> nmschulte: dnkl: I don't see anything in the debian package that would modify files under arbitrary users' homedirs. It would be extremely unorthodox for a package to do that anyway
<dnkl> Arnavion: yeah... it felt like a far fetched idea
<Arnavion> Also, given the latest commit there (because of https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1916321.html ), someone may want to suggest them to rename the terminfos to foot-extra instead of dropping them entirely...
<Arnavion> dnkl: On that note... At least OpenSUSE and Arch are renaming the terminfos to foot-extra* without using `-Ddefault-terminfo` so that foot.ini continues to default to `foot`. What do you think of changing `default-terminfo` / adding another option just for the terminfo names to simplify that?
<dnkl> Arnavion: that's really up to the distributions. With that setup, I imagine they want foot to use the terminfo from ncurses by default, while still providing an *optional* package with "our" terminfo files.
<Arnavion> Yes
<dnkl> I guess we could add another option.
nmschulte has quit [Ping timeout: 250 seconds]
<dnkl> I'm just afraid it'll be too hard to overlook
<dnkl> we already have so many terminfo related options
<Arnavion> Just default-terminfo and custom-terminfo-install-location no?
<dnkl> birger: ^^ (have you considered keeping the foot terminfo package, but with renamed files? That's how many other distributions handle it)
<dnkl> Arnavion: terminfo, default-terminfo and custom.. so three currently. But I guess 'terminfo' is easy enough to understand that it barely counts...
<dnkl> let me think about it
<Arnavion> Well since you're not immediately opposed to it :) do you want me to open an issue to track it?
<dnkl> Arnavion: I already started writing a patch 😅
<dnkl> how about 'terminfo-base-name'. If not set, defaults to 'default-terminfo'
<Arnavion> Yeah, sounds good
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
<birger> dnkl: ah, I haven't. I'll consider it!
cc0_ is now known as cc0
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
nmschulte has joined #foot
newchair has quit [Ping timeout: 252 seconds]
xd1le has joined #foot
<nmschulte> dnkl: thanks. yeah, I am very miffed about this, I have no idea what occurred and as noted it is bothering me.
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
emcconville has quit [Ping timeout: 258 seconds]
emcconville has joined #foot
emcconville has quit [Ping timeout: 245 seconds]
emcconville has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
nmschulte has quit [Ping timeout: 240 seconds]
Ordoviz has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
nmschulte has joined #foot
nmschulte has quit [Read error: Connection reset by peer]
ayushnix has quit [Remote host closed the connection]
ayushnix has joined #foot
<Kabouik_> Really happy with touch support working in 1.15.0. With all the terminal programs I'm using all the time on my phone, even for my email, being able to triple-click to select and to scroll with touch is really cool.
nmschulte has joined #foot
nmschulte has quit [Changing host]
nmschulte has joined #foot
<ifreund> TUI email on a phone is hardcore man
<Kabouik_> I have a 64-key keyboard on my phone ifreund though, game changer
<Kabouik_> I'm talking to you from a terminal IRC client on my phone too :O
Ordoviz has quit [Quit: WeeChat 4.0.2]
nmschulte has quit [Read error: Connection reset by peer]
nmschulte has joined #foot
nmschulte has quit [Ping timeout: 260 seconds]
Armada has joined #foot
nmschulte has joined #foot