jer0me has quit [Read error: Connection reset by peer]
jeromenerf has joined #foot
pranjal has joined #foot
phinxy has quit [Ping timeout: 240 seconds]
pranjal has quit [Ping timeout: 240 seconds]
pranjal has joined #foot
pranjal has quit [Quit: WeeChat 3.4]
cvmn has joined #foot
cvmn has quit [Ping timeout: 276 seconds]
cvmn has joined #foot
cvmn has quit [Ping timeout: 276 seconds]
radu242407821 has joined #foot
florhizome[m] has joined #foot
<florhizome[m]>
Hello :)
<florhizome[m]>
I’m trying to use foot, and I like it so far, but it doesn’t seem to wrap long lines properly for me. text that goes beyond the vertical or horizontal border will be printed in weird ways, whether it’s using a man page or entering a longer pint on a smaller window.
<florhizome[m]>
I’m using gnu guix, I already checked the checkwinsize parameter, it seems to be set “on”
<novakane>
q
<novakane>
oops sorry
<dnkl>
florhizome[m]: do you have a screenshot? Which version of foot? Which terminfo (TERM) are you using?
<florhizome[m]>
foots version is 1.10.3
<florhizome[m]>
I’m using wayfire btw
<florhizome[m]>
maybe the swayfire extension could be involved in this
<florhizome[m]>
I just used the default one, right now I set it to foot-direct to try that out in foot.ini
<dnkl>
florhizome[m]: it's still very unclear what exactly the problem is. A screenshot would be very useuful
<florhizome[m]>
Oh, that actually seems to be the problem.
<florhizome[m]>
kitty and alacritty work though.
<florhizome[m]>
one sec
<florhizome[m]>
wtf it works now
<florhizome[m]>
Even with the plug-in
<dnkl>
florhizome[m]: if it comes back, screenshot it then :)
<dnkl>
fwiw, one difference between foot, and alacritty/kitty, is that the other two are both GPU accelerated, while foot is not. That means they use different mechanisms in Wayland, to handle the rendered surfaces. That _could_ explain why they weren't affected
<florhizome[m]>
I'm not kidding
<florhizome[m]>
The problem was f.e. a line that reaches the border would not be wrapped so it would be printed at a new line, but it would just go on, moving the prompt out of the window. This would cause problems when moving the cursor backwards again and correcting something
<dnkl>
florhizome[m]: that almost sounds as if Wayfire is clipping the window.
<florhizome[m]>
I now restarted wayfire with swayfire (tiling plugin) still enabled.
<florhizome[m]>
Maybe foots terminfo got loaded by the guix home reconfigurations i did.
<dnkl>
this shouldn't have anything to do with the terminfo
<florhizome[m]>
Swayfire, the tiling plugin.
<florhizome[m]>
It's very much alpha
<dnkl>
florhizome[m]: yeah, sounds like it's not communicating the correct window size to foot
<dnkl>
so foot sets one size, and then the plugin clips to a different size
<dnkl>
there's probably a "configure" event that's either missing, or has the wrong dimensions
<florhizome[m]>
I think wayfire hasn't implemented a transaction manager that the swayfire dev is waiting for
<dnkl>
in any case, foot always respects the window size suggested by these "configure" events. So, this *shouldn't* be an issue with foot
<florhizome[m]>
as i said, kitty and alacritty didn't have those issues.
<florhizome[m]>
Hmm.
<dnkl>
are you using CSDs or SSDs?
<florhizome[m]>
SSD
<florhizome[m]>
Wayfire would enforce them the way i use it. Not setting anything from the foot side
<florhizome[m]>
Ah i got it!
<florhizome[m]>
I also installed alacritty, and that caused the value TERMINFO_DIRS to sad
<florhizome[m]>
Basically in guix packages live in shell environments called profiles and you can tell guix that an env var should make a profile export a certain path in it.
<florhizome[m]>
*when it is activated
<dnkl>
florhizome[m]: ok, so... foot couldn't find its terminfo?
<florhizome[m]>
finding the terminfo makes the problem go away.
<florhizome[m]>
do you still want screenshots?
<florhizome[m]>
I will probably send this as an example to guix upstream and a patch to the foot package
<dnkl>
florhizome[m]: no need for a screenshot of you've found the issue :)