this post was submitted on 27 Sep 2023
431 points (96.3% liked)

linuxmemes

21188 readers
823 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 60 points 1 year ago* (last edited 1 year ago) (10 children)

    Why would you ~~pipe~~ edit: redirect neofetch into your .bashrc?

    [–] [email protected] 34 points 1 year ago (2 children)

    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...

    [–] [email protected] 37 points 1 year ago

    But .bashrc is executed, not displayed.

    Maybe they meant to say echo neofetch >> ~/.bashrc.

    [–] [email protected] 23 points 1 year ago* (last edited 1 year ago) (2 children)

    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.

    EDIT: tested out the latter command

    [–] [email protected] 19 points 1 year ago (1 children)

    true!! i meant echo neofetch >> .bashrc

    [–] [email protected] 8 points 1 year ago (1 children)

    Who's the true noob now? Smh

    (/s)

    [–] [email protected] 9 points 1 year ago

    actually. i meant neofetch > bashrc, as in neofetch is better. checkmate

    /s

    [–] [email protected] 4 points 1 year ago

    It's a dangerous command because a single > destroys your .bashrc.

    This is why you have a dotfiles repository, you noob!

    load more comments (7 replies)