From owner-freebsd-chat@FreeBSD.ORG Sun Mar 9 14:38:20 2008 Return-Path: Delivered-To: freebsd-chat@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF5D31065671 for ; Sun, 9 Mar 2008 14:38:20 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 04F808FC26 for ; Sun, 9 Mar 2008 14:38:19 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m29EcIQG070465; Sun, 9 Mar 2008 15:38:18 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m29EcEbr070464; Sun, 9 Mar 2008 15:38:14 +0100 (CET) (envelope-from olli) Date: Sun, 9 Mar 2008 15:38:14 +0100 (CET) Message-Id: <200803091438.m29EcEbr070464@lurza.secnetix.de> From: Oliver Fromme To: freebsd-chat@FreeBSD.ORG, reed@reedmedia.net, josh@tcbug.org, nejc@skoberne.net In-Reply-To: X-Newsgroups: list.freebsd-chat User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Sun, 09 Mar 2008 15:38:18 +0100 (CET) Cc: Subject: Re: WooHoo! 10 years of FreeBSD X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-chat@FreeBSD.ORG, reed@reedmedia.net, josh@tcbug.org, nejc@skoberne.net List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Mar 2008 14:38:20 -0000 Jeremy C. Reed wrote: > > It's also a shell meta-character in the shells I'm familiar with, and > > gets expanded long before grep would ever see it unless you escape it. > > Hence the question about what shell the poster is using.... > > sh, bash, or ksh just pass it a long literally if not matched > > tcsh, csh complain if not match. The error message says the command name > -- but that is bogus -- as the command is never even ran. Really it is the > shell. Just for completeness: zsh is configurable in that regard. When the option "nomatch" is set (the default), it behaves like csh, otherwise it behaves like sh. (There are many more options that configure the globbing behaviour.) Personally I prefer the default behaviour, i.e. giving an error when there is no match. Using unquoted wildcards and relying on the fact that there is no match can be very dangerous. I also often make use of the feature that zsh expands glob expressions when you press tab (or it beeps at you if there is no match). So you can see exactly what files are affected by a command _before_ pressing Enter. That feature has saved me more than once. Just my 2 cents. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "The ITU has offered the IETF formal alignment with its corresponding technology, Penguins, but that won't fly." -- RFC 2549