17:26 <jvoisin> ohai

17:26 <jvoisin> would there be any interest in fuzzing foot a bit?

17:27 <dnkl> jvoisin: absolutely. I've occasionally done very simple, untargeted fuzzing. But a more focused effort would be welcome

17:28 <jvoisin> care to open an issue about this with what you've done so far?

17:33 <dnkl> There's not really much; usually just cat /dev/random. At one point in time I wrote a small python script that generated random sixel images

17:33 <dnkl> (the latter is done by the pgo script as well, but without trying to be malicious)

17:33 <jvoisin> ho, so you're just throwing random things into a terminal

17:47 <dnkl> I did begin setting up proper fuzzing a while back. Can't remember which framework i used. This was before the build was split up the way it is now, and I got stuck on instantiating a terminal and feeding it the fuzzing data. I.e I never got anywhere with it

17:48 <jvoisin> yeah, that was my main concern

17:48 <jvoisin> and I was wondering if you have a way to "instantiate" a terminal, and just feed it data to see if it crashes

17:48 <jvoisin> without having to use a real one

17:49 <dnkl> Technically yes, but there's a lot of dependencies. Might want to take a look at pgo/pgo.c

17:50 <jvoisin> ack

17:56 <dnkl> jvoisin: regarding your sixel question; the short answer is yes, I'd accept a patch to disable it at compileh-time

17:56 <dnkl> Will post full reply on codeberg later

17:57 <jvoisin> not at runtime?

18:00 <dnkl> Maybe. If it can be done without affecting performance

18:01 <dnkl> And it probably can. Just need to stop recognizing the sixel escapes

18:02 <jvoisin> yup

18:02 <jvoisin> thanks ♥

23:10 <codebam> hi my clipboard copy stops working when I copy something to my clipboard in chromium. how do I fix that?