darcy@sh.itjust.works to linuxmemes@lemmy.world · 1 year agocomputersh.itjust.worksimagemessage-square6fedilinkarrow-up175arrow-down13
arrow-up172arrow-down1imagecomputersh.itjust.worksdarcy@sh.itjust.works to linuxmemes@lemmy.world · 1 year agomessage-square6fedilink
minus-squareradix@lemm.eelinkfedilinkarrow-up10·1 year agoWhy would you pipe neofetch into your .bashrc?
minus-squarelco@kbin.sociallinkfedilinkarrow-up4·1 year 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-squareraubarno 🇱🇹@lemmy.mllinkfedilinkarrow-up3·edit-21 year 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-squareradix@lemm.eelinkfedilinkarrow-up1·1 year agoBut .bashrc is executed, not displayed. Maybe they meant to say echo neofetch >> ~/.bashrc.
Why would you pipe 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
But .bashrc is executed, not displayed.
Maybe they meant to say
echo neofetch >> ~/.bashrc.