this post was submitted on 05 Dec 2024
814 points (96.9% liked)
linuxmemes
21632 readers
39 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
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think that a lot of people are missing this, my first Windows was Windows XP, so I'm pretty much used to doing everything through a GUI
Same, but I learned (rather quickly mind you) enough of the CLI to get by, and continue learning to this day. I looked up a few "Bash basics" and "linux terminal basics" videos on youtube and followed along like it was a class which really helped. And whenever I have to figure out how to solve an issue I have (for instance my airpods didn't want to connect through the GUI at first) and it gives me a CLI fix (bluetoothctl in this case) I try to remember it, or I can always go "ah fuck what was that command again.." and search it again, or I put some of those in a textfile called linuxcommands.txt that I can reference back to, or I can try
bluetoothctl -h
for help, orman bluetoothctl
for the manual for bluetoothctl (and that works with most CLI programs.) Honestly sometimes I prefer the CLI now.Now I need to learn all of the symbols and hotkeys and for loops and cool shit like that, but I'll get there.