public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to prevent documentation in /usr/share/doc  from being bzip2'ed ?
Date: Fri, 31 Oct 2008 10:24:36 +0000	[thread overview]
Message-ID: <20081031102436.0f57e5af@digimed.co.uk> (raw)
In-Reply-To: <20081031003855.GA9216@crowfix.com>

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

On Thu, 30 Oct 2008 17:38:55 -0700, felix@crowfix.com wrote:

> On Thu, Oct 30, 2008 at 07:39:10PM -0400, Eric Martin wrote:
> > Why not go even easier and use bzcat,bzless,zcat,and zless
> 
> Because bzgrep and many others haven't been written.

Shhh, don't tell my computer that!

[nelz@krikkit ~ 0]% which bzgrep
/usr/bin/bzgrep
[nelz@krikkit ~ 0]% qfile bzgrep
app-arch/bzip2 (/usr/bin/bzgrep)


-- 
Neil Bothwick

"Bother," said Pooh, as the media exposed his sexual depravity.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-10-31 10:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 13:43 [gentoo-user] How to prevent documentation in /usr/share/doc from being bzip2'ed ? Ashish Shukla आशीष शुक्ल
2008-10-30 14:01 ` Albert Hopkins
2008-10-30 14:02 ` Daniel Pielmeier
2008-10-30 22:24   ` Ashish Shukla आशीष शुक्ल
2008-10-30 22:55     ` Albert Hopkins
2008-10-30 23:39       ` Eric Martin
2008-10-31  0:12         ` Neil Bothwick
2008-10-31  0:38         ` felix
2008-10-31  5:49           ` Paul Hartman
2008-10-31 10:24           ` Neil Bothwick [this message]
2008-10-30 23:51       ` Ashish Shukla आशीष शुक्ल
2008-10-30 22:50 ` Iain Buchanan
2008-10-30 23:48   ` Ashish Shukla आशीष शुक्ल
2008-10-31  2:50     ` Iain Buchanan
2008-10-31  0:40   ` felix
2008-10-31  2:23     ` Andrey Falko
2008-10-31  5:42       ` felix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081031102436.0f57e5af@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox