darcy to linuxmemes@lemmy.world • 9 months agocomputersh.itjust.worksimagemessage-square47fedilinkarrow-up1452arrow-down118
arrow-up1434arrow-down1imagecomputersh.itjust.worksdarcy to linuxmemes@lemmy.world • 9 months agomessage-square47fedilink
minus-squarelcolinkfedilink34•9 months 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-squareradixlinkfedilink37•9 months agoBut .bashrc is executed, not displayed. Maybe they meant to say echo neofetch >> ~/.bashrc.
minus-squareraubarnolinkfedilink24•edit-29 months 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-squaredarcyOPlinkfedilink9•9 months agoactually. i meant neofetch > bashrc, as in neofetch is better. checkmate /s
minus-square@Rodeo@lemmy.calinkfedilink4•9 months ago It’s a dangerous command because a single > destroys your .bashrc. This is why you have a dotfiles repository, you noob!
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…
But .bashrc is executed, not displayed.
Maybe they meant to say
echo neofetch >> ~/.bashrc.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 >> .bashrcWho’s the true noob now? Smh
(/s)
actually. i meant neofetch > bashrc, as in neofetch is better. checkmate
/s
This is why you have a dotfiles repository, you noob!