darcy to linuxmemes@lemmy.world • 2 years agocomputersh.itjust.worksimagemessage-square29fedilinkarrow-up128arrow-down10
arrow-up128arrow-down1imagecomputersh.itjust.worksdarcy to linuxmemes@lemmy.world • 2 years agomessage-square29fedilink
minus-squareradixlinkfedilink2•edit-22 years agoWhy would you pipe edit: redirect neofetch into your .bashrc?
minus-squarelcolinkfedilink3•2 years agoso that everytime you launch a terminal, your neofetch data is displayed. Because wow, neofetch!!! It doesn’t really make sense, since the data would be outdated anyway if piped into .bashrc that way…
minus-squareraubarnolinkfedilink1•edit-22 years agoIt won’t work. It’s a dangerous command because a single > destroys your .bashrc. You may want either echo 'neofetch' >> .bashrc or neofetch | sed -e 's:%:a:g' | sed -e "s:^\\(.*\\)$:printf '\1\\\\n':" >> .bashrc or something of that kind. EDIT: tested out the latter command
minus-square@Rodeo@lemmy.calinkfedilink1•2 years ago It’s a dangerous command because a single > destroys your .bashrc. This is why you have a dotfiles repository, you noob!
minus-squareradixlinkfedilink1•2 years agoBut .bashrc is executed, not displayed. Maybe they meant to say echo neofetch >> ~/.bashrc.
Why would you
pipeedit: redirect neofetch into your .bashrc?so that everytime you launch a terminal, your neofetch data is displayed. Because wow, neofetch!!!
It doesn’t really make sense, since the data would be outdated anyway if piped into .bashrc that way…
It won’t work. It’s a dangerous command because a single
>destroys your.bashrc. You may want eitherecho 'neofetch' >> .bashrcorneofetch | sed -e 's:%:a:g' | sed -e "s:^\\(.*\\)$:printf '\1\\\\n':" >> .bashrcor something of that kind.EDIT: tested out the latter command
true!! i meant
echo neofetch >> .bashrcThis is why you have a dotfiles repository, you noob!
But .bashrc is executed, not displayed.
Maybe they meant to say
echo neofetch >> ~/.bashrc.That’s a redirection, not a pipe.