• kibiz0r@midwest.socialEnglish
    3·
    9 months ago

    2GB dotfile repo

    being lost without vim keybinds

    Im_in_this_picture_and_I_dont_like_it.png

    I use macOS btw

    • darcy@sh.itjust.worksOP
      11·
      7 months ago

      it is actually a 200 IQ meme. your average coomfiger doesnt know that much about shell scripting, but thinks they do.

      or something. i definitely didnt get it wrong myself

  • radix@lemm.ee
    2·
    9 months ago

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

    • lco@kbin.social
      4·
      9 months ago

      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…

      • radix@lemm.ee
        2·
        9 months ago

        But .bashrc is executed, not displayed.

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

      • raubarno@lemmy.ml
        1·
        9 months ago

        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

  • CaptainBasculin@lemmy.ml
    2·
    9 months ago

    i had i3 run with no problems on some of the worst machines I had to use. I’ll fight with anyone that claims i3 is bloat.

  • Andrew@mander.xyz
    1·
    9 months ago

    Akchually, binary prefixes are the one and only correct prefixes for counting digital size of information (GiB instead of GB).

    • Rodeo@lemmy.ca
      1·
      9 months ago

      Good old conky lol. Its like it was made to be a config playground, and the actual functionality was an afterthought.