From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@coraid.com>
Date: Mon,  5 Oct 2009 12:24:57 -0400
To: 9fans@9fans.net
Message-ID: <7980ce1ef1a3d761e56c7ef111341699@coraid.com>
In-Reply-To: <200910051708.aa33544@salmon.maths.tcd.ie>
References: <20091003160327.GA15021@nipl.net>
	<7359f0490910031001s3354e29awfb916f953bb96ec@mail.gmail.com>
	<20091003183127.GC15021@nipl.net>
	<200910051708.aa33544@salmon.maths.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] mishandling empty lists - let's fix it
Topicbox-Message-UUID: 7f01c914-ead5-11e9-9d60-3106f5b1d025

> I've learned to avoid
> globbing as much as possible.  In any shell with command
> substitution globbing is unnecessary, and is often dangerous.
> I would happily use a shell with NO globbing, just to avoid
> another source of worries.

i think this is all a bit dramatic.

there are very simple idioms one can
use in the few cases globbing may be
a problem.  others have suggested ./<pattern>
and i'd add that one can also use
	if(! ~ <pattern> '<pattern>')
		something;
but this is seldom necessary.  one
might consider having the file server
ban globbing characters in file names.

if i could roll back time, i would push
for regular expressions instead of the
goofy shell matching.  then knuth could
have to say that unix is 29 definitions of
regular expressions living under one roof.
:-)

- erik