• @dot@sopuli.xyz
    link
    fedilink
    32 years ago
    nfetch() {
        echo ""
    	echo "$USER @ $(hostname)"
    	echo ""
    	echo "kernel : $(uname -r)"
    	echo "uptime : $(uptime -p)"
    	echo "pkgs   : $(dpkg -l | grep '^ii' | wc -l)"
    	echo "bat    : $(acpi -b | grep -Po '(?<=: ).*(?=,)' | tr -d '[:space:]') " 
    	# need to install acpi to run bat
    	echo ""
    } 
    
    • @Rodeo@lemmy.ca
      link
      fedilink
      12 years ago

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

  • @kibiz0r@midwest.social
    link
    fedilink
    English
    22 years ago

    2GB dotfile repo

    being lost without vim keybinds

    Im_in_this_picture_and_I_dont_like_it.png

    I use macOS btw

      • dditty
        link
        fedilink
        12 years ago

        This post is what is giving me the idea to finally set up a dotfiles repo for the first time.

  • Free Palestine 🇵🇸
    link
    fedilink
    21 year ago

    If you do neofetch > .bashrc you will simply have a broken shell config. To add neofetch to the bashrc you need to use echo.

    • darcyOP
      link
      fedilink
      11 year 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
    link
    fedilink
    2
    edit-2
    2 years ago

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

    • lco
      link
      fedilink
      32 years 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…

      • raubarno
        link
        fedilink
        1
        edit-2
        2 years 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

        • @Rodeo@lemmy.ca
          link
          fedilink
          12 years ago

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

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

        • darcyOP
          link
          fedilink
          12 years ago

          true!! i meant echo neofetch >> .bashrc

      • radix
        link
        fedilink
        12 years ago

        But .bashrc is executed, not displayed.

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

  • Andrew
    link
    fedilink
    12 years ago

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

  • CaptainBasculin
    link
    fedilink
    12 years 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.