🚀 go-pugleaf

Gregory L Hansen (ghansen@isc.sjsu.edu) wrote:
: In article <pecora-2202961305350001@lou-pecora.nrl.navy.mil>,
: Louis M. Pecora <pecora@zoltar.nrl.navy.mil> wrote:
: >In article <4gi5lf$rid@nuke.csu.net>, ghansen@isc.sjsu.edu (Gregory L
: >Hansen) wrote:
: 
: >> I know, it's right there in man with everything else.  Somewhere.  And 
: >> easy enough to find if you read the whole friggin' database starting from 
: >> page 1!
: >
: >man > file1 | grep "core" \"[a-z]*& >> stdout < &
: 
: Of course!  Why didn't I see that?  I guess they were right.  It's easy.

Because you are _not_ a complete idiot? I mean, it's fun to make fun of
UNIX, but at least get it right --- there is a double redirection at the
very beginning, plus an incomplete redirection at the end (which would,
were it complete, also conflict with the pipe).

What you really do is either

man -k whatyouarelookingfor 

or you use the equivalent

apropos whatyouarlookingfor 

(it might be easier to remember). Or you write a script (once) which 
goes along the lines of

  for a in `echo $MANPATH | tr ":" " "` 
  do grep $1 $a/* /dev/null
  done

which will tell you quickly where to look for the info.

Bernie

P.S.: The above script is absolutely straighforward, and you can
      assume that any Visual Basic code is equally "complex" to
      write and understand, if not more so.