Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-AuthUser: gerrit:koeln.convey.de Date: Sun, 16 Mar 2003 16:45:35 +0100 From: "Gerrit P. Haase" Reply-To: "Gerrit P. Haase" Organization: Esse keine toten Tiere X-Priority: 3 (Normal) Message-ID: <106670116606.20030316164535@familiehaase.de> To: "mellman AT txm5 DOT local" CC: cygwin AT cygwin DOT com Subject: Re: two problems w/ new perl encountered In-Reply-To: <20030314224647.A765@txm5.local> References: <200303141606 DOT h2EG6O319858 AT mailgate5 DOT cinetic DOT de> <14512692592 DOT 20030314210151 AT familiehaase DOT de> <20030314224647 DOT A765 AT txm5 DOT local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id h2GFfuF07315 Hallo mellman, Am Freitag, 14. März 2003 um 22:46 schriebst du: > Is there a way to dump the exact pipeline that perldoc uses? > It says something in the man page about nroff, etc ... > Does it use nroff or groff? /usr/bin/nroff From perldoc -h: Options: -t Display pod using pod2text instead of pod2man and nroff (-t is the default on win32) So the problem probably is hidden somewhere in pod2man. Gerrit -- =^..^=