Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
A good start is to install
tldr
. You use it likeman
, but it gives you shorter explanations – or rather, a short list of illustrative examples.As for man pages themselves (which I often find overwhelming, too), if you're not doing that already, you can pipe it into
grep
to extract just those lines that contain your search string:Going further, check out Fish instead of Bash. I haven't use Fish yet, but it's said to be much better for learning Linux commands as a beginner. Later on, you may switch to Zsh. In any case, hitting Tab once or twice will often give you a list of possible completions to the command you are typing.
PS: I see no good reason why anyone should downvote this question.
Edit (June 23): As it so happens, just today I've stumbled into the O'Reilly book "Classic Shell Scripting" by Robbins and Beebe (ISBN 9780596005955). What can I say – its age notwithstanding, it's apparently an extremely good book for understanding things and learning how to solve real problems. (It presupposes some familiarity with Unix-like systems and with the shell, so if one's just starting out, the book "Learning the Unix Operating System" may be better.)
I do have tldr and fish and love it ! Although I get a little annoyed that my aliases from bash didn't carry over into fish because I sometimes forget to launch fish since I almost always use the ctrl alt t shortcut to launch term
You can change your default shell in a few ways. I've never used fish, but
vipw
should open yourpasswd
file, in which you can change/bin/bash
to the appropriate path for fish (which you can find viawhich fish
). It's probably best to only change this for your user.A possibly simpler option (and one that I don't believe requires root access) is the
chsh
command. I've never used it myself, so I'll let this site provide instructions for it: https://www.howtogeek.com/669835/how-to-change-your-default-shell-on-linux-with-chsh/Article by a Red Hat engineer that also makes a ton of contributions to FOSS in their free time: Don't change your login shell, use a modern terminal emulator
Interesting, I hadn't heard that take. I'll give it a read. Thanks!
My pleasure fam! Btw, I'm in no place to dictate what's right or wrong (or whatsoever). I just wanted to add their perspective on the matter*.
I don't know that I agree with the take represented in your linked article. If I'm reading it correctly, the primary reason not to switch shells is that those shells might not exist universally. That is a valid concern, but running
which fish
(as referenced in my original comment) should help to mitigate that risk factor. Scripts should always use a hashbang to specify their desired environment so, unless you're overriding that, it shouldn't be a concern.I agree that you shouldn't use shells that are not available to you. I don't think that means you shouldn't try to change shells if you are unsatisfied with your current one.