It 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.
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…
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)
This is why you have a dotfiles repository, you noob!
That's a redirection, not a pipe.