dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.10.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
lechner has quit [Ping timeout: 268 seconds]
lechner has joined #foot
lechner has quit [Ping timeout: 250 seconds]
lechner has joined #foot
taylor85345 has joined #foot
taylor85345 has quit [Client Quit]
taylor85345 has joined #foot
<taylor85345> Hi all, I'm having an issue with foot persistently warning that my font is not monospace, even though it is. Characters are also rendered very spread out. I have tried a variety of monospace fonts, and the issue persists.
<taylor85345> I'm running a relatively fresh Garuda install, and of the three systems I have foot installed on, this is the only one presenting this issue
<taylor85345> I currently have it configured with "DejaVu Sans Mono"
<manio> taylor85345: you can check and compare the console log - if it differ for selected font on all your systems...
<manio> that way you can see if the font is indeed the same on all systems
<manio> of course I assume you have same config on those...
<taylor85345> my other running system has the font just set as "monospace" in my config. This was also the default on this system as well, and was presenting the issue.
<taylor85345> I should have gotten on earlier...I've run out of time tonight. Will try again later and so some comparisons...
taylor85345 has quit [Quit: WeeChat 3.3]
novakane has joined #foot
gtms has joined #foot
<dnkl> "monospace" isn't a specific font, and may resolve to a non-monospace font. Foot's stdout will show which font that actually got loaded
<rj1> foot rules
<hexa-> uh, oh. foot 1.10.1 just crashed on me
<hexa-> #0 0x0000000000429402 in set_pivot_point_for_block_and_char_wise.lto_priv ()
<hexa-> #1 0x00000000004295e8 in selection_update ()
<hexa-> no symbols, no further usable stack trace
<hexa-> if it happens again I'll try and rebuild with debug symbols
<dnkl> hexa-: thanks, please do!
<dnkl> hexa-: you were doing a mouse selection?
<hexa-> using sway, I was switching to the desktop with the terminal in question
<hexa-> I can't exactly remember, I'm on a laptop, so my touchpad may have done any kind of silly things
<dnkl> hexa-: I took a quick look, and one thing I found was that foot wouldn't "finalize" (stop) an ongoing selection on point leave events
<dnkl> So, if you switched workspace *away* from foot
<dnkl> While doing a mouse selection
<dnkl> And then switched back
<dnkl> Foot would try to continue your previous mouse selection
<dnkl> I wouldn't bet any money on that this is what happened in your case, but it's at least something
<hexa-> played around with selection and desktop switches but no cras
<hexa-> h
novakane has quit [Quit: WeeChat 3.3]
novakane has joined #foot
Lord has quit [Ping timeout: 250 seconds]
Lord has joined #foot
novakane has quit [Quit: WeeChat 3.3]
gtms has quit [Remote host closed the connection]
<Nulo> Since upgrading PipeWire I get this: err: modules/alsa.c:235: failed to attach to card
<Nulo> (yambar)
<Nulo> alsamixer works fine