Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The cd command is probably one of the first 10 that any Linux user learns, but it's not the only way to navigate the Linux file system.Here are some other ways.
Whether you're moving around the file system, looking for files or trying to move into important directories, Linux can provide a lot of help. In this post, we'll look at a number of tricks to make moving around the file system and both finding and using commands that you need a little easier.
Anyhow, the second article is, maybe a little bit, too quickly written. In the output to “help | less”, or “help -d” some descriptions are terribly unhelpful, clipped or otherwise “defunct”. I would not have dared to just replicate this output. You absolutely need the “help [cmd]” in these cases. But you do not know, why.., so why..?
Ah! This is cool, too:
“Sample outputs:”
Quote:
:: :
Null command.
No effect; the command does nothing.
Exit Status:
Always succeeds
Well... thank you. Maybe. Or What... for the sample.
No. Really. I did not even know the “help” command. This is great stuff, all in all.
Last edited by Michael Uplawski; 03-31-2020 at 07:55 AM.
Reason: Sample outputs, second article, not the first.
Anyhow, the second article is, maybe a little bit, too quickly written. In the output to “help | less”, or “help -d” some descriptions are terribly unhelpful, clipped or otherwise “defunct”. I would not have dared to just replicate this output. You absolutely need the “help [cmd]” in these cases. But you do not know, why.., so why..?
Ah! This is cool, too:
“Sample outputs:”
Well... thank you. Maybe. Or What... for the sample.
No. Really. I did not even know the “help” command. This is great stuff, all in all.
I really cannot see why you would pipe 'help | less' since the help output would be a page. The 'help command' would be to use the 'help shopt' as an example;
Quote:
help shopt
shopt: shopt [-pqsu] [-o] [optname ...]
Set and unset shell options.
Change the setting of each shell option OPTNAME. Without any option
arguments, list all shell options with an indication of whether or not each
is set.
Options:
-o restrict OPTNAMEs to those defined for use with `set -o'
-p print each shell option with an indication of its status
-q suppress output
-s enable (set) each OPTNAME
-u disable (unset) each OPTNAME
Exit Status:
Returns success if OPTNAME is enabled; fails if an invalid option is
given or OPTNAME is disabled.
As most experienced users know that 'help' is abbreviated to allow a user to get description for a particular command.
I thought the articles would be helpful to some Gnu/Linux users.
Hope this helps.
Have fun & enjoy Gnu/Linux!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.