Xref: utzoo comp.lang.perl:1674 comp.unix.wizards:22695
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!schaefer
From: schaefer@ogicse.ogc.edu (Barton E. Schaefer)
Newsgroups: comp.lang.perl,comp.unix.wizards
Subject: Re: Looking for balanced critique of Perl
Message-ID: <10240@ogicse.ogc.edu>
Date: 29 Jun 90 17:57:02 GMT
References: <4811@muffin.cme.nist.gov> <8497@jpl-devvax.JPL.NASA.GOV> <814@ehviea.ine.philips.nl>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 21

In article <814@ehviea.ine.philips.nl> leo@ehviea.UUCP (Leo de Wit) writes:
} In article <8497@jpl-devvax.JPL.NASA.GOV> lwall@jpl-devvax.JPL.NASA.GOV (Larry Wall) writes:
}     [stuff left out...]
} |With many of the questions that people ask in comp.lang.perl,
} |I just search through the man page using the very keyword they used,
} |and find the thing right there in the manual.
} 
} Unfortunately, the very keyword you're looking for is often underlined,
} or typed over multiple times, so it contains embedded backspaces (and
} possible underscores or repetitions) in the manual text. I had a few
} bad experiences with that lately. There really should be an option of
} the pager to compare modulo underlining/fat printing.

I have taken to using

    man perl | less -i

Searches in the "less" pager, at least in more recent versions, will match
underlined or overstruck text when the ignore-case option is used.
-- 
Bart Schaefer						schaefer@cse.ogi.edu