urosm has quit [Remote host closed the connection]
urosm has joined #foot
eqb_ has joined #foot
eqb has quit [Remote host closed the connection]
eqb_ is now known as eqb
neurocyte has quit [Ping timeout: 276 seconds]
neurocyte has joined #foot
neurocyte has quit [Changing host]
neurocyte has joined #foot
urosm has quit [Remote host closed the connection]
an3223 has quit [Remote host closed the connection]
an3223 has joined #foot
ptrc has quit [Remote host closed the connection]
ptrc has joined #foot
puida has quit [*.net *.split]
stu- has quit [*.net *.split]
alebastr has quit [*.net *.split]
beerman has quit [*.net *.split]
WhyNotHugo has quit [*.net *.split]
sefidel has quit [*.net *.split]
kaisan has quit [*.net *.split]
flowji has quit [*.net *.split]
llyyr has quit [*.net *.split]
alebastr has joined #foot
WhyNotHugo has joined #foot
beerman has joined #foot
stu- has joined #foot
kaisan has joined #foot
flowji has joined #foot
llyyr has joined #foot
sefidel has joined #foot
puida has joined #foot
puida has quit [Max SendQ exceeded]
WhyNotHugo has quit [Max SendQ exceeded]
puida has joined #foot
WhyNotHugo has joined #foot
jknr has quit [*.net *.split]
diaspora39 has quit [*.net *.split]
jknr has joined #foot
diaspora39 has joined #foot
an3223 has quit [Ping timeout: 260 seconds]
urosm has joined #foot
azerov has quit [Quit: Gateway shutdown]
alexherbo2 has joined #foot
<dnkl>
urosm: not sure. We get every key press, but that only tells us the key, not its function
<dnkl>
i.e. we'll see Alt was pressed, but I don't know if we can see that the *function* 'compose' is active or not
<dnkl>
I would have to look through the xkb API
<dnkl>
what we can get from XKB is whether we're currently composing something. I.e. if we're in the middle of a compose key sequence. I assume it will say we are as soon as the compose key has been pressed, and stay so until the final, composed character has been printed
<dnkl>
it will however also "trigger" for dead key sequences
<dnkl>
also not sure how we'd render this in foot, as we don't have an UI. Only thing I can think of is an alternative cursor
an3223 has joined #foot
urosm has quit [Remote host closed the connection]
urosm has joined #foot
urosm has quit [Remote host closed the connection]
cbb has joined #foot
urosm has joined #foot
urosm has quit [Remote host closed the connection]
urosm has joined #foot
<dnkl>
I'm planning to do a new foot release soon. I want to wait a couple of days to see if there will be any more changes to the OSC-99 specification
<dnkl>
lots of new additions to it recently
alexherbo2 has quit [Remote host closed the connection]
tsdh has joined #foot
<tsdh>
Is there a way to test foot themes quickly, e.g., by somehow loading it in an existing foot window?
<j`ey>
(I wrote my own, but still does the same thing with OSC11)
<tsdh>
OMG, 448 themes. How should I ever come to a decision?!
<j`ey>
thats only 448 they include
<tsdh>
Isn't it strange that probably half of all light themes seem to have serious glitches, e.g., for them either Color 0 or Color 15 (and sometimes some color in between) is equal to the background?
<j`ey>
I think it's somewhat outdated, afaik alacritty does damage tracking now (but Im not sure how that plays into the actual rendering part)
<dnkl>
but they still render the full frame, every time? Their damage tracking is what it reports to the compositor, right?
<j`ey>
ah
<neurocyte>
yeah, I've read the performance page. but I don't feel it tells the whole story. in my testing foot renders fully change frames with faster frame rates and less CPU than alacritty or ghostty and is almost exactly on par with kitty
<neurocyte>
damage tracking doesn't really explain that
<dnkl>
GPU's are magical. For full frames, it all depends on how many cores you have, and which GPU you have, and how they compare
<dnkl>
GPU's are *not* magical
<dnkl>
😅
<dnkl>
foot has one of the, of not the fastest VT parsers out there. A lot of work has been done there, very low level work (taking into account cache behavior, CPU write buffers etc)
<dnkl>
then there's fcft, the font rasterizer used by foot, which is more or less designed to support foot's use case
<dnkl>
but, regardless of which emulator you compare with, there will always be use cases where someone else is faster
urosm has quit [Read error: Connection reset by peer]
urosm has joined #foot
urosm has quit [Remote host closed the connection]
vyivel has joined #foot
<neurocyte>
nice! it looks like foot supports OSC 2027. you might want to mention that somewhere on the website
<dnkl>
you mean private mode 2027? It's not an OSC sequence
<dnkl>
it's listed in our ctlseqs man page
<neurocyte>
ah, for some reason I don't have the foot-ctlseqs page on arch linux
<rockorager>
neurocyte: master branch has both in-band resize and fancy underlines (the latter would be nice for flow)
<delthas>
rockorager: since there were significant updates to the osc 99 spec, i suggest to keep my patch open/unmerged until i submit a new version
<delthas>
on vaxis i mean
<rockorager>
delthas: will do. thanks for the heads up
<rockorager>
Kovid made updates to the spec?
<delthas>
yeah a lot of changes
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
urosm has joined #foot
urosm has quit [Remote host closed the connection]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]