caveman has quit [Remote host closed the connection]
caveman has joined #foot
Nulo has quit [Ping timeout: 252 seconds]
an3223 has joined #foot
ynakao has quit [Quit: WeeChat 3.4]
ynakao has joined #foot
ynakao has quit [Quit: WeeChat 3.4]
ynakao has joined #foot
ynakao has quit [Quit: WeeChat 3.4]
ynakao has joined #foot
an3223 has quit [Ping timeout: 240 seconds]
an3223 has joined #foot
brocellous has quit [Ping timeout: 240 seconds]
brocellous has joined #foot
ghost08 has joined #foot
<ghost08>
hi guys, I want to find the procedure with which I can tell foot, that it needs to wait with rendering until all my text and sixel data is printed out. I know there was something new that only foot can do. but somehow I can't find it
<dnkl>
Ah, sorry. Saw the PR but haven't had time to look at the diff
<cbb>
no worries
<cbb>
I've just changed the Sync cap in terminfo
<cbb>
and added a note to thr DCS sequence
<cbb>
should be no functional changes
<dnkl>
cbb: looks good, though I won't pretend I'm fluent in terminfo speak... But I assume you've tested it?
<cbb>
dnkl: yeah, I've tested it
<cbb>
it maps "1" to "h" (DECSET) and "2" to "l" (DECRST)
<cbb>
so that it's compatible with the old "API"
<cbb>
you can test with "tput Sync 1" and observe the timeout delay
<cbb>
but let me do some more serious testing before we merge
<dnkl>
cbb: sounds reasonable (re terminfo API)
<dnkl>
Did a quick search in kitty and contour, to see if they use 2026 in 'Sync', but couldn't find anything (wanted so see if they did something else with the parameters)
<cbb>
I think the people who came up with the number did some searching for that
<dnkl>
Sure, but I meant if they did something different in their terminfo's Sync definition, with the "parameters" (i.e we assume '1' and '2' right now, to be compatible with the DCS)
<cbb>
dnkl: ah ok, yeah I see what you mean
<cbb>
it was the tmux author who came up with the terminfo string