Mac Os X Man Pages
The Mac OS X mmap man page says that it is possible to allocate superpages and I gather it is the same thing as Linux huge pages. Open a file or folder. The open command opens a file (or a folder or URL), just as if you had double-clicked the file's icon. Syntax open options -b bundleidentifier -a application file. A ``component package' contains payload to be installed by the OS X Installer. Although a component package can be installed on its own, it is typically incorporated into a product archive, along with a ``distribution&#. Pkgbuild(1) osx man page. Mac OS September 15, 2010 Mac OS. All times are GMT -4. The time now is 10:12 PM. NewerXY file True if the current file has a more recent last access time (X=a), change time (X=c), or modification time (X=m) than the last access time (Y=a), change time (Y=c), or modification time (Y=m) of file. In addition, if Y=t, then file is instead inter- preted as a direct date specification of the form understood by cvs(1). GUI for Man pages on Mac OS X. It captures a list of all Man pages on the system, allows for searches by keyword and also a viewer within which to read and scroll. While the Terminal will do.
| Click here to return to the 'Yet another way to read beautifully formatted man pages' hint |
Personally, I like to use the following. The output is in plain text rather than a pretty webpage, but it is instantaneous, requires no network connection, and gives you all the functions and convenience of TextEdit (or whatever other text editor you choose to use) while working with man pages.
Just add the following lines to .profile (or .bash_profile or whatever applies to your situation) in your home folder.
For those of who like to use vim:
vman()
{
man '${1}' | col -bx | view -
}
Actually, if you're using vim, put this into your .vimrc:
and then, from inside vim, you can type ':Man whatever' (yes, the M must be uppercase) to get nice syntax-colored (you do have syntax on in your .vimrc, right?) man pages in a split window inside vim. Great for referring to documentation while writing scripts.
Oh, and if you haven't checked out a recent version of MacVim, definitely give it a whirl -- it's awesome (best version of the best text editor ever, and it's free).
This is what I settled on using MacVim:
function tman {
man '${1}' | col -b | /usr/local/bin/gview - 1>/dev/null 2>&1
}
Thanks for your suggestion -- you're right about the speed, and of course yours works offine. I added that too and now I have both.
To support the non-numeric man sections, such as 'n' (for Tcl commands), change your regex to:
.*(${1}.)([[:alnum:]]).*$
All 1 2 3 4 5 6 7 8 9 n to your local home page. 
There are also some excellent man page reading apps out there, but they require launching and browsing a list.
Not necessarily. Using Bwana I can just type 'open man:gethostbyname' and instantly see the output in my web browser. It also has searching capabilities. If I'm already in the browser, I can just type 'man:gethostbyname' in the address field.
The only problem with Bwana I've found is that if you click on a man link from within Xcode documentation, it opens the man page in Xcode documentation, but also tries to open it in Bwana, but fails. It is annoying but not too big a deal since, while in X code documentation, I typically don't need to lookup man pages.
I like bwana too, because I use Firefox and search by typing. Very fast. From there you can print the PDF. It generates an index, which I've bookmarked.
I've always used the following, in this case for 'dscl', without the %:
% man -t dscl | pstopdf -i -o ~/Desktop/dscl.pdf
It should be noted that this hint does not display the man pages content stored on your hard drive, therefore it may not display the correct man page for the version of the app that is installed on your computer. For example, if you've installed a more recent version of rsync, this hint will load Apple's rsync man page which describes the behavior of the version of rsync included in Mac OS X, and that may have different options than the one you're running locally.
as pointed out in the comments on the PDF hint - the key to making this a great option is to cache the PDFs - they then open instantly after a one time conversion.
Will work when your offline - while this one won't
-P
Looks like I'm the only one still using good old 'man'. :)
Type '/word' to search for 'word', press N to go to the next hint and navigate with vim-like controls (F, B, J, K, g, G), that's all I need. :)
---
this is not the sig you`re looking for.
I use an AppleScript to accomplish this (using pstopdf -> Preview) but in addition to the lookup, for a quicker response next time, I store the results of each unique man page in a folder in ~/Documents. My script then checks that folder first for the term entered and does a man -t lookup of the term only if it's not already on file.
function niceman { man -t $@ | open -f -a Preview.app; } This makes man output PostScript and Preview will convert it to a PDF. On large man pages it may take a few seconds, but on small ones it's nice and quick. All the formatting comes through looking very good.
Mac Os X Man Pages
As an example, I timed 'niceman bash' from the time I hit enter to the time I saw the PDF open in Preview - it took around 5 seconds to generate a 64-page PDF.
---
k:.
My thoughts exactly. In the Terminal it's just 'manopen zsh' to open the corresponding formatted and linked man page. And you can leave it open while crafting your command-line.
Try it and see, if you don't like it then go back to the ugly Times-Roman uselessly-paginated non-hyperlinked PDF files.
---
Madness takes its toll.
Please have exact change.
The wealth of information on this forum is fantastic.
man -w twice, but that's to avoid any temporary variables - YMMV. Create, add files to, or extract files from an archive file in gnutar format, called a tarfile. Tape ARchiver; manipulate 'tar' archive files.
tar creates and manipulates streaming archive files.
This implementation can extract from tar, pax, cpio, zip, jar, ar, and ISO 9660 cdrom images and can create tar, pax, cpio, ar, and shar archives.
The first synopsis form shows a 'bundled' option word. This usage is provided for compatibility with historical implementations. See COMPATIBILITY below for details.
In -c, -r, or -u mode, each specified file or directory is added to the archive in the order specified
on the command line. By default, the contents of each directory are also archived.
In extract or list mode, the entire command line is read and parsed before the archive is opened.
The pathnames or patterns on the command line indicate which items in the archive should be processed.
Patterns are shell-style globbing patterns as documented in tcsh(1).
Environment
The following environment variables affect the execution of tar:
LANG The locale to use. See environ(7) for more information.
TZ The timezone to use when displaying dates. See environ(7) for more information.
Exit Status
The tar utility exits 0 on success, and >0 if an error occurs.
Examples
Mac Os X Man Pages Download
To tar and zip a file
To view a detailed table of contents for this archive:
To tar a folder (with all sub-folders and files)
The reverse process to extract the file
Extract a file, autodetecting the format, in this case an xz archive:
To extract all the C sources and headers from an archive named backup.tar:
Note that the pattern must be quoted to prevent the shell from attempting to expand it according the files in the current working directory (the shell does not have access to the list of files in the archive, of course).
To move file hierarchies, use a command line like this:
To create a compressed archive on diskette, using gzip(1), use a command-line like:
Note that you cannot mix bundled flags and --style flags; you can use single-letter flags in the manner above, rather than having to type tar --block-compress --gzip --verbose --file /dev/fd1a --block-size 20 tar/
The above-created diskette can be listed with
tar tvfbz /dev/fd1a 36
To join two gnutar archives into a single archive, use
tar Af archive1.tar archive2.tar
which will add the files contained in archive2.tar onto the end of
archive1.tar (note that this can't be done by typing:
cat archive2.tar >> archive1.tar
because of the end-of-file block at the end of a gnutar archive).
To archive all files from the directory srcdir, which were modified after
Feb. 9th 1997, 13:00 h, use
Notes
Always tar -t before tar -x to check if the archive contents have been placed inside one subdirectory or will just spill all over the current directory.
The -C feature does not work like historical gnutar programs, and is probably untrustworthy.
The -A command should work to join an arbitrary number of gnutar archives together, but it does not; attempting to do so leaves the end-of-archive blocks in place for the second and subsequent archives.
The gnutar file format is a semi fixed width field format, and the field for device numbers were designed for 16 bit (8 major, 8 minor) and can not absorb our 32 bit (8 major, 16+8 minor) numbers.
Environment Variables
'To disarm the bomb simply enter a valid tar command on your first try. No Googling' ~ XKCD
Related macOS commands:
bzip2(1)
cpio - Copy files to and from archives.
compress - compress and expand data.
gzip - Compress or decompress files.
pax(1)
rmt - remote magtape protocol module.
info tar
Equivalent Windows command: TAR - Store, list or extract files in an archive.
Some rights reserved