• radix
    61•9 months ago

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

    • lco
      34•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
        37•9 months ago

        But .bashrc is executed, not displayed.

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

      • raubarno
        24•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

        • darcyOP
          18•9 months ago

          true!! i meant echo neofetch >> .bashrc

        • @Rodeo@lemmy.ca
          4•9 months ago

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

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

  • @kibiz0r@midwest.socialEnglish
    40•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

    • fmstratAEnglish
      3•9 months ago

      Also looking at my dotfiles repo…

      • ditty
        3•9 months ago

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

  • @CaptainBasculin@lemmy.ml
    23•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.

    • @Rodeo@lemmy.ca
      5•9 months ago

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

      • @mattomattic@discuss.tchncs.deEnglish
        1•9 months ago

        Afterthought is an understatement. I didn’t mind piping some of that info into an i3 status bar, but just a couple things. Who needs to watch all that distracting system stuff all the time. Using autocompletions on the command line would get that info quick enough. And whoever down voted my original comment - I’m laughing about it. Serious business right?

    • PropaGandalf
      26•9 months ago
      • Has over 100 obscure USE flags he forgot what they do
      • Needs two days to configure his kernel and two more to compile it.
      • Uses ancient thinkpad
      • Uses lynx because firefox won’t compile
      • Uses rusty old software because of “tradition”
      • Uptime ~30 years
      • umbraroze
        30•9 months ago

        Uptime ~30 years

        Too generous for Gentoo.

        “Maybe if I tweak the kernel config juuuuust a little bit today” “Is it just me or did this particular version of gcc make the kernel 0.0002% slower? I need to do some tests” “…Dunno, it just feels slower today, I guess I need to recompile the whole system”

        Uptime: 30 minutes, tops

  • @MigratingtoLemmy@lemmy.world
    10•9 months ago

    I write in POSIX shell as a matter of principle.

    My “dotfiles” repo is a few Kb in size.

    I am too dumb and lazy to try Nix.

    I do like using vim keybindings in my terminal.

    Neofetch is bloat, I wrote a script that shows some essential information when the machine starts and that’s it.

  • Andrew
    6•9 months ago

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

  • Free Palestine 🇵🇸
    2•7 months 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
      0•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