alias_qr_rainmaker@lemmy.world to linuxmemes@lemmy.world · 2 days agocat posttitle.txt | grep memelemmy.worldimagemessage-square48linkfedilinkarrow-up1357arrow-down15
arrow-up1352arrow-down1imagecat posttitle.txt | grep memelemmy.worldalias_qr_rainmaker@lemmy.world to linuxmemes@lemmy.world · 2 days agomessage-square48linkfedilink
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up5·2 days agoWell, when I can just do $EDITOR file…
minus-squarejayands@lemmy.worldlinkfedilinkarrow-up2·2 days agoThe subtle difference is that your $SHELL is responsible for opening (and, iirc, parsing?) the file when you use \<, versus the $EDITOR being the responsible entity.
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up1·1 day agoOh I get it now. Also, for some reason setting vi as $EDITOR, it is not able to load the contents of the file, unlike vim that does.
minus-squaresomerandomperson@lemmy.dbzer0.comlinkfedilinkarrow-up4·2 days agowe’re talking about a pipeline(-ish) thing here. so just out the cmd that you want to read the output of in the brackets
Well, when I can just do
$EDITOR file…The subtle difference is that your $SHELL is responsible for opening (and, iirc, parsing?) the file when you use
\<, versus the $EDITOR being the responsible entity.Oh I get it now.
Also, for some reason setting
vias$EDITOR, it is not able to load the contents of the file, unlikevimthat does.we’re talking about a pipeline(-ish) thing here.
so just out the cmd that you want to read the output of in the brackets