Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: Krzysztof Duleba Subject: Re: man - broken pipe Date: Wed, 20 Jul 2005 10:33:10 +0200 Lines: 24 Message-ID: References: <42DE0998.DB8F6E09@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) In-Reply-To: <42DE0998.DB8F6E09@dessent.net> X-IsSubscribed: yes Brian Dessent wrote: > Krzysztof Duleba wrote: > >>After some updates I get broken pipe messages when pressing 'q' to exit >>from less. The man pages are printed correctly. > > I think that is by design and not a bug. When you are viewing the > manpage, a pipeline of commands has been setup to decompress and format > the manpage. Because 'less' doesn't ask for more input until you page > down, it means that those commands are all blocked waiting to consume > their input and produce more output. If you quit 'less' before reaching > the end, the pipeline is broken and the commands all receive SIGPIPE. > It's normal and harmless. If you don't want to see the message you can > hit 'end' or '>' before quitting less. It doesn't happen with small > manpages because they probably fit entirely in a single buffer. I get this error on my laptop and only since I've updated most packages few days ago. I don't get this on Linux boxes and on Windows box with Cygwin updated the last month. Hitting 'end' or '>' helps indeed. I wonder what makes the difference that now SIGPIPE is delivered and has visible effects. Krzysztof Duleba -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/