I’ve just been looking through a few man pages for a few different commands including grep and ifconfig. I’ve noticed over a few pages, the content uses a strange syntax to notate what i think are quotations (back-tick followed by a single or double quote): `text' Why can’t they use ‘ or ” to open … Read more
After downloading the source code for Bash, I was browsing through the doc directory and came across the following files:
By default, man uses less to output text. How can I tell it to just output to stdout? My terminal emulator has a scroll bar and search function and I want to use those instead of the arrow keys.
Sometimes I need to look up certain words through all the manual pages. I am aware of apropos, but if I understand its manual right, it restricts search to the descriptions only.
So in a recent fit of folly, I followed the instructions in this answer on the Ubuntu SE page since I wanted to remove most of the documentation. However, I didn’t read the commands well enough and missed that that those would also remove the man pages, which I didn’t want.
Typing man alias gives me
apropos works great for searching manual page names and descriptions. Is there a similar command for searching the entire contents of the manual pages?
Both hier(7) and file-hierarchy(7) man pages claim to describe the conventional file system hierarchy. However, there are some differences between them. For example, hier(7) describes /opt and /var/crash, but file-hierarchy(7) does not. What are the differences between these two descriptions. Which one do real Linux systems use?
I came across a sentence in vimdoc:
A man page for fork, for example, is in the System Calls section that has number 2: