Ignacio@lemmy.ml to Linux@lemmy.ml · 1 year agoThe only cheat sheet you needcheat.shexternal-linkmessage-square18fedilinkarrow-up1118arrow-down15
arrow-up1113arrow-down1external-linkThe only cheat sheet you needcheat.shIgnacio@lemmy.ml to Linux@lemmy.ml · 1 year agomessage-square18fedilink
minus-squaretal@lemmy.todaylinkfedilinkarrow-up3·1 year agoI’m more-inclined to blame a virtual terminal than the program writing the sequences if there’s an exploit there.
minus-squareArthur Besse@lemmy.mlMlinkfedilinkarrow-up2·1 year agoOf course the terminal emulators are ultimately to blame but when there are so many problems in so many of them, imo curl’s default behavior should be to filter its output when writing to a tty.
minus-squarekraniax@lemmy.wtflinkfedilinkarrow-up1·1 year agois there a curl argument that can be used to block this behavior?
I’m more-inclined to blame a virtual terminal than the program writing the sequences if there’s an exploit there.
Of course the terminal emulators are ultimately to blame but when there are so many problems in so many of them, imo curl’s default behavior should be to filter its output when writing to a tty.
is there a curl argument that can be used to block this behavior?