From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.161]) by krisdoz.my.domain (8.14.5/8.14.5) with ESMTP id q179eFgD018891 for ; Tue, 7 Feb 2012 04:40:17 -0500 (EST) X-RZG-AUTH: :JiIXek6mfvEEUpFQdo7Fj1/zg48CFjWjQv0cW+St/nW/afgnrylsiW++ZjV6rmQ= X-RZG-CLASS-ID: mo00 Received: from britannica.bec.de (ip-109-45-189-68.web.vodafone.de [109.45.189.68]) by smtp.strato.de (cohen mo43) (RZmta 27.6 DYNA|AUTH) with (DHE-RSA-AES128-SHA encrypted) ESMTPA id Q002c7o178XLNW for ; Tue, 7 Feb 2012 10:39:57 +0100 (MET) Received: by britannica.bec.de (sSMTP sendmail emulation); Tue, 07 Feb 2012 10:39:53 +0100 Date: Tue, 7 Feb 2012 10:39:53 +0100 From: Joerg Sonnenberger To: discuss@mdocml.bsd.lv Subject: Dealing with compressed man pages Message-ID: <20120207093953.GB15446@britannica.bec.de> X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Hi all, at the moment, it is the responsibility of the man(1) frontend and similar programs to handling uncompressing man pages. They generally do this by building a pipe to "preprocess" the man page with zcat, just like they did with tbl(1). Given that we removed most needs for such a pipeline and there are at least two frontends dealing with man pages (apropos/makewhatis and man), I wonder if it wouldn't simplify things if the decompressing is done as part of the file loop. Detecting zlib/gzip is trivial and the amount of code small as well. I don't think the parallelism is noticable even on modern system due to the small man page size. Comments? Joerg -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv