Why would you ~~pipe~~ edit: redirect neofetch into your .bashrc?
this post was submitted on 27 Sep 2023
435 points (96.2% liked)
linuxmemes
21355 readers
1337 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
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...
But .bashrc is executed, not displayed.
Maybe they meant to say echo neofetch >> ~/.bashrc.
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
true!! i meant echo neofetch >> .bashrc
Who's the true noob now? Smh
(/s)
actually. i meant neofetch > bashrc, as in neofetch is better. checkmate
/s
It's a dangerous command because a single
>destroys your.bashrc.
This is why you have a dotfiles repository, you noob!
That's a redirection, not a pipe.
Good catch.
Exactly, that's bloat
2GB dotfile repo
being lost without vim keybinds
Im_in_this_picture_and_I_dont_like_it.png
I use macOS btw
Also looking at my dotfiles repo...
This post is what is giving me the idea to finally set up a dotfiles repo for the first time.
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.
i love i3
Too smart for NixOS - LMAO! I bet this guy has a conky on his Blackbox.
Good old conky lol. Its like it was made to be a config playground, and the actual functionality was an afterthought.
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?
Average OpenBSD user
OpenBSD users:
Neofetch and NixOS are bloat.
Arch's X setup sucks, sx is better.
Also, 2 GB of dotfiles is bloat
Must be pretty bad spaghetti code.
But I can't have sx if I use Linux ;(
I do use sx in Arch, though?
It was just an attempt at a dumb stereotypical joke that Linux users don't have sex
Almost and not always average Gentoo user
- 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
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
True I didn't take this into account. On the other hand we have systemd soft-reboot now.
Gentoo users don't use systemd.
Bold assumption you did here...
Most Gentoo users use OpenRC.
you forgot the cooling pad it's on since the fans died like a decade 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.
based.
Akchually, binary prefixes are the one and only correct prefixes for counting digital size of information (GiB instead of GB).
acckshually, i dont use 'Giga' or 'Mega', i just use bits, in scientific notation: 2.0*10^9
That wouldn't be 2 GB, that would be 2 Gb
GB would be 2.0*10^9*8 bits
uhhh uhhh what's more bloated than windows 10 uhhhhhhhhhhhhhhhhh i honestly don't know
windows 11
nooo that has smaller icon's mabye windows 8 start screen
If you do neofetch > .bashrc you will simply have a broken shell config. To add neofetch to the bashrc you need to use echo.
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