home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!rutgers!cmcl2!cs!fox
- From: fox@cs.nyu.edu (David Fox)
- Newsgroups: comp.os.linux
- Subject: Re: "man" :command not found
- Message-ID: <FOX.93Jan2232620@graphics.nyu.edu>
- Date: 3 Jan 93 04:26:20 GMT
- References: <1993Jan2.230541.4428@cbfsb.cb.att.com>
- Sender: notes@cmcl2.nyu.edu (Notes Person)
- Organization: Courant Institute of Mathematical Sciences
- Lines: 29
- In-Reply-To: wto@cbnewsg.cb.att.com's message of Sat, 2 Jan 1993 23:05:41 GMT
- Nntp-Posting-Host: graphics.cs.nyu.edu
-
- In article <1993Jan2.230541.4428@cbfsb.cb.att.com> wto@cbnewsg.cb.att.com (William T. O Connell) writes:
-
- I have been having no problem with man in the past, but after
- updating to .99p2, get the following message.
-
- $man uucp
- : command not found
- $
-
- This just started to happen with the updated version (.99p2), though
- I wouldn't think that it would have anything to do with it???
-
- If I pass some bogus manual page name to man, it says man page not
- found as expected.
-
- Any clues what started causing this? (I'm stumped)
-
- I had a problem because I was setting the PAGER environment
- variable to the empty string. I was getting the message
- "Syntax error" because I was trying to read compressed man
- pages, which constructs the command "$EXPANDER filename | $PAGER"
- but if you try to read uncompressed man pages with
- PAGER set to the empty string you will probably get the
- message you are getting. Change to PAGER=cat. (I don't
- user PAGER=less because I read my man pages in emacs.)
- There is an easy fix to man-1.1 which I should report to
- the FSF.
-
- -david
-