From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: slightly ot
Date: Sat, 20 Jan 2007 19:06:47 +0100 [thread overview]
Message-ID: <200701201906.48793.bo.andresen@zlin.dk> (raw)
In-Reply-To: <loom.20070120T184310-371@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
On Saturday 20 January 2007 18:46, James wrote:
> Daniel Iliev <danny <at> ilievnet.com> writes:
> > eix -C -c -n media-video | grep -i dvd
>
> That's a pretty cool search string.
> If I wanted to search the entire tree, why does this not work?
>
> eix -C -c -n * | grep -i dvd
>
> eix does not expand wildcards for matches?
It would be helpful if you would take just one look at `man eix` to see what
the arguments do.
-n isn't necessary since eix will automatically disable colors when it detects
a pipe (the | sign). -c just makes the output more compact. -C means you're
specifying a category but * isn't a category..
Furthermore if you type the above command (assuming you're using bash) eix
doesn't get an * at all because bash expands it before ever executing the
command. Try typing `echo *` to see what bash expands it to.
But no, even if you escaped or quoted the * properly eix doesn't expand it.
But if you don't use --exact it always assumes wildcards. Hence `eix -C -c
video` results in the same output as `eix -C -c media-video`. And `eix -c`
outputs everything in the tree.
Instead of the silly grep above I'd just search descriptions with -S though...
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-20 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 14:33 [gentoo-user] slightly ot Kellystewart00
2007-01-20 15:11 ` Thomas Lingefelt
2007-01-21 6:03 ` Kellystewart00
2007-01-20 15:39 ` Daniel Iliev
[not found] ` <loom.20070120T184310-371@post.gmane.org>
2007-01-20 18:06 ` Bo Ørsted Andresen [this message]
[not found] ` <200701201949.10080.volker.armin.hemmann@tu-clausthal.de>
2007-01-21 0:45 ` b.n.
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=200701201906.48793.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--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