Why would you
pipeedit: redirect neofetch into your .bashrc?61 0 Replyso 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...
35 1 ReplyBut .bashrc is executed, not displayed.
Maybe they meant to say
echo neofetch >> ~/.bashrc
.37 0 ReplyIt won't work. It's a dangerous command because a single
>
destroys your.bashrc
. You may want eitherecho 'neofetch' >> .bashrc
orneofetch | sed -e 's:%:a:g' | sed -e "s:^\\(.*\\)$:printf '\1\\\\n':" >> .bashrc
or something of that kind.EDIT: tested out the latter command
24 0 Reply
That's a redirection, not a pipe.
12 0 ReplyGood catch.
4 0 Reply
Exactly, that's bloat
2 0 Reply
2GB dotfile repo
being lost without vim keybinds
Im_in_this_picture_and_I_dont_like_it.png
I use macOS btw
42 2 ReplyAlso looking at my dotfiles repo...
3 0 ReplyThis post is what is giving me the idea to finally set up a dotfiles repo for the first time.
3 0 Reply
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.
25 2 Replyi love i3
14 1 Reply
Too smart for NixOS - LMAO! I bet this guy has a conky on his Blackbox.
21 1 ReplyGood old conky lol. Its like it was made to be a config playground, and the actual functionality was an afterthought.
5 0 ReplyAfterthought 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?
1 0 Reply
Average OpenBSD user
18 0 ReplyOpenBSD users:
17 0 ReplyNeofetch and NixOS are bloat.
Arch's X setup sucks, sx is better.
15 1 ReplyAlso, 2 GB of dotfiles is bloat
14 0 ReplyMust be pretty bad spaghetti code.
5 0 Reply
But I can't have sx if I use Linux ;(
6 0 ReplyI do use sx in Arch, though?
4 0 Reply
Almost and not always average Gentoo user
13 0 Reply- 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
27 0 ReplyUptime ~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
30 0 Replyyou forgot the cooling pad it's on since the fans died like a decade ago
4 0 Reply
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.
10 0 Replybased.
2 1 Reply
Akchually, binary prefixes are the one and only correct prefixes for counting digital size of information (GiB instead of GB).
6 0 Replyacckshually, i dont use 'Giga' or 'Mega', i just use bits, in scientific notation: 2.0*10^9
4 0 ReplyThat wouldn't be 2 GB, that would be 2 Gb
GB would be 2.0*10^9*8 bits
2 0 Reply
uhhh uhhh what's more bloated than windows 10 uhhhhhhhhhhhhhhhhh i honestly don't know
4 0 Replywindows 11
6 0 Replynooo that has smaller icon's mabye windows 8 start screen
2 0 Reply