On Fri, 10 Apr 2020 12:37:56 -0400, Jack wrote:
> Even eix often finds things I think are irrelevant, but I know it's
> searching on a regexp, so I'll often do "eix ^string$ if I know the
> package and am just looking for the info about it.
Use eix -e if you want an exact match.
--
Neil
On 4/10/20 10:08 AM, Grant Edwards wrote:
Yes, I'm aware I can add "--fuzzy-search n" to make it act sane, but
is there an environment variable or USE flag or _something_ to make
emerge --search do the right thing by default?
Does adding it to EMERGE_DEFAULT_OPTS in /etc/portage/make.conf
On 2020.04.10 12:21, Alec Ten Harmsel wrote:
On Fri, Apr 10, 2020, at 12:08, Grant Edwards wrote:
> I really, really hate how emerge now returns bucketfulls of useless,
> unrelated results when you do a search. WTF is the point of
returning
> a bunch of packages that don't contain the search
On Fri, Apr 10, 2020, at 12:08, Grant Edwards wrote:
> I really, really hate how emerge now returns bucketfulls of useless,
> unrelated results when you do a search. WTF is the point of returning
> a bunch of packages that don't contain the search string when there is
> is a package name that
I really, really hate how emerge now returns bucketfulls of useless,
unrelated results when you do a search. WTF is the point of returning
a bunch of packages that don't contain the search string when there is
is a package name that match the search string exactly?
Yes, I'm aware I can add
5 matches
Mail list logo
