New answers tagged man
I would suggest if 'less' fails to clear the screen that you put: alias less='(less; clear)' in your ~/.profile or /.bashrc. (I am not on a linux machine to test this at the moment, but this should work in bash.)
Why not just clear the screen on exit? man man; clear
Normally less "clears the screen" (which probably refers to switching back to the normal screen from the alternate screen) when the terminal description has the appropriate escape sequence in the rmcup capability. You would see a difference if you are using different values of TERM in the two programs. The infocmp program can show differences for the ...
The mention of LESS_TERMCAP_so was incomplete. That is less's special environment variable used to override the termcap so (standout) capability. To use this capability, you have to provide a se (standend) capability as well. The terminfo(5) manual page gives a summary of these features for terminfo (smso/rmso) and termcap (so/se) names: ...
I do this all the time. This command line makes me happy: man man | col -bx > man.txt col -b removes backspaces. col -bx also replaces tabs with spaces which is my strong preference. If I want the text to be formatted to a width of my preference while reading, then I change the command to this: MANWIDTH=10000 man man | col -bx > man.txt
Indeed in this context "online" means "on a computer" as opposed to printed on paper. Source: I was responsible for getting new versions of those manuals printed and reproduced at the MIT Lab for Computer Science back in the 70s.
The word "on-line" is used in the sense "operating under the direct control of, or connected to, a main computer." Reading a manual "on-line" is therefore the same as reading it "on the computer". This is in contrast to "off-line" in the sense "operating independently of, or disconnected from, an associated computer." Reading a manual "off-line" is ...
In contrast to a printed (hard-copy) manual, which you could read off-line (while not using a computer). The term dates back (at least) to time-sharing systems. Users may have had a terminal which could be used for typing text, punching paper tapes. But they were only able to use the computer when they were on-line (the "line" referring to the ...
ls -alh is the same as ls -a -l -h. Multiple short options can be combined like this. Here are the meanings of those options from man ls: -a, --all do not ignore entries starting with . -l use a long listing format -h, --human-readable with -l, print sizes in human readable format (e.g., 1K 234M 2G)
-h stands for human readable. As mentioned in the comment, you can combine arguments simply like: -alh. The order is irrelevant. From man ls: -h, --human-readable with -l and/or -s, print human readable sizes (e.g., 1K 234M 2G)
The â is an artifact of using UTF-8 characters without handling them properly. That's the first byte of multiple bytes in a UTF-8 character. If the terminal is setup to know about UTF-8, it combines those bytes on the screen so you can read it. You can fix this for PuTTY by setting the translation to UTF-8. Further reading: 4.10.1 Controlling character ...
on OSX the man pages are stored on /usr/share/man/man5/. Some of them are already installed (e.g. for fstab). But for e.g. tar it isn't. Unfortunately there's no libarchive-dev package on homebrew. A workaround for just the man pages is to download the libarchive sourcecode for the version which is installed (tar --version) and copy the man pages over: ...
Man section 5 is "File Formats and Conventions" and is not installed by default. see What do the numbers in a man page mean? To install part of it on a Debian system, install: sudo apt-get install libarchive-dev From packages.debian.org: Package: libarchive-dev (3.1.2-11+deb8u1) The libarchive library provides a flexible interface for reading ...
On a Fedora 22 system: # rpm -qf /usr/share/man/man5/tar.5.gz libarchive-3.1.2-14.fc22.x86_64 So try updating libarchive.
You should not have to manually set MANPATH on a Mac. Unlike most Unix-based systems, OS X automatically selects an appropriate search path for man pages based on the contents of PATH. The rules for this are described in the section "Search Path for Manual Pages" in manpath(1). The configuration file for this has been in other locations in the past, but ...
Often, a man page is referenced via suffixing it with the section enclosed in parentheses, e.g.: read(2) This style has two main advantages: it is immediately clear that you reference a man page - i.e. you can write something like 'cf. read(3)' instead of 'cf. the section 3 man page of read' if multiple sections contain man pages with the same name, ...
Top 50 recent answers are included