X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,BAYES_40,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Subject: RE: man redirect error Date: Fri, 6 Jan 2012 07:56:00 -0600 Message-ID: <2BF01EB27B56CC478AD6E5A0A28931F203C953F4@A1DAL1SWPES19MB.ams.acs-inc.net> In-Reply-To: <1325707977.7212.4.camel@raker2.ateb.com> References: <1325707977 DOT 7212 DOT 4 DOT camel AT raker2 DOT ateb DOT com> From: "Nellis, Kenneth" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id q06DuINn029038 On Wed, 2012-01-04 at 08:51 -0600, Thrall, Bryan wrote: > Perhaps the OP was looking for something like apropos or whatis? > > In this case, the OP was simply using "head" as an example to show how piping the output of man was generating an unexpected error. As you all know, Unix is rich in text processing tools, so it shouldn't be a surprise that one might want to do some processing of man output. Further experimentation with piping man output suggests that the error presents itself when the process receiving the man output stream terminates (as with head) before man is done writing it. --Ken Nellis