From owner-freebsd-current Fri Apr 17 17:57:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25761 for freebsd-current-outgoing; Fri, 17 Apr 1998 17:57:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA25676 for ; Sat, 18 Apr 1998 00:57:31 GMT (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.8/8.8.7) with ESMTP id BAA21776; Sat, 18 Apr 1998 01:41:09 +0100 (BST) (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199804180041.BAA21776@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Eivind Eklund cc: current@FreeBSD.ORG Subject: Re: Bug in sh? In-reply-to: Your message of "Fri, 17 Apr 1998 19:37:37 +0200." <19980417193737.36274@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Apr 1998 01:41:08 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [.....] > #!/bin/sh > . < `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. If the above syntax was ok, then command | . would also be ok (although the same as ``command | sh'' unless you're running a *real* ksh) :-/ Anyway, it just looks weird. > Eivind. -- Brian , , 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