Date: Sat, 16 Mar 2002 12:08:45 +1100 From: "Tim J. Robbins" <tim@robbins.dropbear.id.au> To: Luigi Rizzo <rizzo@icir.org> Cc: hackers@FreeBSD.ORG Subject: Re: weird sh behaviour Message-ID: <20020316120845.A3882@descent.robbins.dropbear.id.au> In-Reply-To: <20020315162609.B93253@iguana.icir.org>; from rizzo@icir.org on Fri, Mar 15, 2002 at 04:26:09PM -0800 References: <20020315162609.B93253@iguana.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 15, 2002 at 04:26:09PM -0800, Luigi Rizzo wrote: > /bin/sh seems not to expanding metacharacters in filenames used for > I/O redirection: *snip* > Is it a feature or a bug ? From my understanding of the POSIX standard, pathname expansion (globbing etc.) should be performed on the word following the > or <, and the result is undefined if more than one file name matches the pattern. FWIW Solaris /bin/sh does not expand, /bin/ksh does, ksh93 does, zsh does. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020316120845.A3882>