Date: Sat, 18 Apr 1998 02:29:47 +0100 From: Brian Somers <brian@Awfulhak.org> To: Eivind Eklund <eivind@yes.no> Cc: Brian Somers <brian@Awfulhak.org>, current@FreeBSD.ORG Subject: Re: Bug in sh? Message-ID: <199804180129.CAA24475@awfulhak.org> In-Reply-To: Your message of "Sat, 18 Apr 1998 03:07:26 %2B0200." <19980418030726.52891@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sat, Apr 18, 1998 at 01:41:08AM +0100, Brian Somers wrote:
> > [.....]
> > > #!/bin/sh
> > > . <<EOF
> > > `SHELL=sh && export SHELL && tset -s -Q \?$TERM < /dev/tty`
> > > EOF
> > [.....]
> > > The second version doesn't work - it exits immediately, and seems to
> > > run tset _after_ the shell has quit.
> >
> > This isn't a bug as you describe it. IMHO, the bug is that the shell
> > doesn't complain that you've failed to pass ``.'' a file name.
>
> My fault. I always forget that <<EOF doesn't expand to a temporary filename
> (as it ought to, and used to in my old world), but instead is just one more
> way of putting things at stdin.
>
> . still shouldn't just continue, and run the command in a second fork
> . _after_ the initial shell script has quit. That _has_ to be a bug?
Agreed.
> Eivind.
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199804180129.CAA24475>