Documentation 101

Find out how to get that @*&^$&@ thing to compile!

Documentation 101

Postby jasont » Thu Aug 16, 2001 6:17 am

Note: By the time you read this apex will probably have made a binary [img]images/icons/wink.gif"%20border="0[/img]

You should have noticed that there are a few ways to get information on commands in unix and in the finder.

1) Mac Help Center
2) Html documents
-a tip here is to go to the directory you want, type pwd, copy the output path and paste that into your browser
3) man <command>
-man -w <command> will show you the location of the manual you are loading.
-man man is worth a read
-you can read nonpathed man files like this
nroff -man <dir>/<filename> | less
4) <command> --help
-this sometimes gives you a help screen
5)<command> this is last resort because sometimes you run a command this way instead of getting "usuage"

But I can't read the documentation for <command>

There are 2 file formats that are not native to the readers in mac os x

6) POD (plain old documentation) these files are converted to man files when you install the with make. However, should you wish to read them you can issue the command

pod2man <filename.pod> | nroff -man | <pager>

Where pager is something like more

7) What's this info stuff and why can't I see the man pages for this new command ex: tar that I just installed.

You may see a directory called info in your directory structure. This contains files readable with texinfo (TeX files).

You can find the webpage for it here <A HREF="http://www.fsf.org/software/texinfo/texinfo.html" TARGET=_blank>http://www.fsf.org/software/texinfo/texinfo.html</A>

As I recall this was prettymuch a straightforward install

*starts apex countdown 11:21:23 PM PST
-j
*stops ob1 timer at 1:42:01 AM PST might have been earlier than that [img]images/icons/wink.gif"%20border="0[/img]
[ August 15, 2001: Message edited by: jasont ]

[ August 16, 2001: Message edited by: jasont ]
jasont
 
Posts: 50
Joined: Tue Aug 14, 2001 7:00 pm
Location: Palo Alto, CA

Re: Documentation 101

Postby jasont » Fri Aug 17, 2001 7:04 am

8: When I do info <command> it doesn't show the information. There is probably a fix to this that adds <command> to the index table, but you can always do
<BLOCKQUOTE><font size="1" face="Verdana, Helvetica, sans-serif">code:</font><HR><pre>
info --file=automake.info
</pre>[/quote]
This example was from the info directory, but standard paths should work.
-j
jasont
 
Posts: 50
Joined: Tue Aug 14, 2001 7:00 pm
Location: Palo Alto, CA

Re: Documentation 101

Postby jayce » Mon Aug 27, 2001 5:45 am

For the point (2), there is a simplier way :
just type
"open -a OmniWeb.app thefile.html" and it will open OmniWeb on the file specified...
The "-a Application" is optionnal, it is just to specify an app, if not specified, the default app for this type will be used...
--
Jayce Piel
Les site des serveurs sous MacOS X:
jayce
 
Posts: 2
Joined: Sun Aug 26, 2001 7:00 pm

Re: Documentation 101

Postby jasont » Sun Sep 02, 2001 4:50 am

[img]images/icons/smile.gif"%20border="0[/img] I was trying to remember how to do that Thanks a lot! JP
jasont
 
Posts: 50
Joined: Tue Aug 14, 2001 7:00 pm
Location: Palo Alto, CA


Return to Compile Problems

Who is online

Users browsing this forum: No registered users and 7 guests

cron