<jmcantrell>
sentriz: have the previous prompts scrolled out of view? that was the only way it would jump for me
<sentriz>
jmcantrell: aah, thanks. but them what's the prev/next about? or how can I have more than one prompt
<jmcantrell>
sentriz: i'm not sure what you mean about more than one. it simply scrolls the output so that the prompt is in view, i think. i haven't used that feature much
cvmn has quit [Ping timeout: 258 seconds]
cvmn has joined #foot
cvmn has quit [Ping timeout: 258 seconds]
cvmn has joined #foot
xd1le has joined #foot
Ordoviz has joined #foot
Ordoviz has quit [Ping timeout: 246 seconds]
Ordoviz has joined #foot
bgs has joined #foot
bgs has quit [Remote host closed the connection]
Ordoviz has quit [Ping timeout: 252 seconds]
Ordoviz has joined #foot
Ordoviz has quit [Ping timeout: 250 seconds]
Ordoviz has joined #foot
talismanick has quit [Ping timeout: 240 seconds]
Ordoviz has quit [Quit: WeeChat 3.7.1]
cvmn has quit [Ping timeout: 258 seconds]
cvmn has joined #foot
dviola has joined #foot
cvmn has quit [Ping timeout: 258 seconds]
cvmn has joined #foot
udent has joined #foot
testuser[m] has joined #foot
<testuser[m]>
Is there some convenient tracing/logging to make foot tell what data exactly it's receiving from programs? I'm trying to investigate why yash (https://yash.osdn.jp/) makes foot output extra $ signs at startup: https://0x0.st/o3QK.png
<testuser[m]>
it only happens at font size > 11 so ig it's some wrapping that's going on but idk what could be causing it to wrap
<Arsen>
I had this issue for a while where, if long lines are present in scrollback, it could result in graphical glitches when scrolling up
<Arsen>
i.e. the wrong lines show up
<Arsen>
I discounted it for a while as "nvidia drivers are crap" but it just happened on my nvidia laptop
<Arsen>
sorry I lack better information - I wanted to put this out there immediately so I don't forget, but can't make concrete reproduction steps immediately
<dnkl>
Arsen: which compositor?
<Arsen>
kwin both times actually
<dnkl>
then I think it's a known issue, fixed in master but not yet released