SHΛRK@lemmy.zip to Programmer Humor@programming.dev · 4 days agoLinux Catlemmy.zipexternal-linkmessage-square62linkfedilinkarrow-up1430arrow-down18file-text
arrow-up1422arrow-down1external-linkLinux Catlemmy.zipSHΛRK@lemmy.zip to Programmer Humor@programming.dev · 4 days agomessage-square62linkfedilinkfile-text
minus-squareranzispa@mander.xyzlinkfedilinkarrow-up11arrow-down1·3 days agoFair, but in general I find it way more useful to use cat for piping. In most cases I’ll do something like cat file | program cat file | program | grep cat file | program | grep | cut This gets more complicated if the file is at the end of the command.
minus-squarea_non_monotonic_function@lemmy.worldlinkfedilinkarrow-up1·2 days agoI don’t know why anybody would disagree with this. It’s a very clean way of putting it.
minus-squaredan@upvote.aulinkfedilinkarrow-up10arrow-down2·3 days agoIt wouldn’t be at the end, since you’d still be piping into program program <file | grep | cut
minus-squarejxk@sh.itjust.workslinkfedilinkarrow-up15·3 days agoAnd <file program | grep | cut works too
Fair, but in general I find it way more useful to use cat for piping.
In most cases I’ll do something like
cat file | program cat file | program | grep cat file | program | grep | cutThis gets more complicated if the file is at the end of the command.
I don’t know why anybody would disagree with this. It’s a very clean way of putting it.
It wouldn’t be at the end, since you’d still be piping into
programprogram <file | grep | cutAnd
<file program | grep | cutworks tooOh, thanks! Didn’t know that
Thanks - I didn’t know this either!