From owner-freebsd-ports  Tue Feb  6  1: 8:34 2001
Delivered-To: freebsd-ports@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id 902E237B684; Tue,  6 Feb 2001 01:08:16 -0800 (PST)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f1698BV10202;
	Tue, 6 Feb 2001 01:08:11 -0800 (PST)
	(envelope-from jkh@winston.osd.bsdi.com)
To: Maxim Sobolev <sobomax@FreeBSD.org>
Cc: Peter Pentchev <roam@orbitel.bg>, ports@FreeBSD.org,
	jkh@FreeBSD.org, Edwin Groothuis <mavetju@chello.nl>
Subject: Re: Request for comments [Fwd: bin/24695: [patch] pkg_info: prefix search for a package] 
In-Reply-To: Message from Maxim Sobolev <sobomax@FreeBSD.org> 
   of "Tue, 06 Feb 2001 10:30:47 +0200." <3A7FB637.792D33D8@FreeBSD.org> 
Date: Tue, 06 Feb 2001 01:08:11 -0800
Message-ID: <10197.981450491@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> but was away from e-mail) ;). What do you think if I reimplement 'fuzzy' and
> 'prefix' options from original proposal into `glob' and `regex' options? So
> regex kidz would be able say "-x .*foo.*", while glob-lovers "-g *foo*".

I love it.  You could even make -g "implicit", e.g. I don't see any
reason why "pkg_info emacs*" shouldn't just work, right?  The only
time you really need to pass a flag is to indicate a particular type
of globbing, e.g. regex.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message