From owner-freebsd-chat Sun Jan 30 17:52:14 2000 Delivered-To: freebsd-chat@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id B1D0614E21 for ; Sun, 30 Jan 2000 17:52:08 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id CAA22958 for freebsd-chat@freebsd.org; Mon, 31 Jan 2000 02:52:07 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA70604 for freebsd-chat@freebsd.org; Mon, 31 Jan 2000 01:06:13 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: GUIs are flawed Date: 31 Jan 2000 01:06:12 +0100 Message-ID: <872jlk$24u3$1@bigeye.rhein-neckar.de> References: <38942CA0.2D5C@funbox.demon.co.uk> To: freebsd-chat@freebsd.org Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <38942CA0.2D5C@funbox.demon.co.uk>, > I would include 'expect' in the toolchest; In a word, no. expect(1) is a hack to forcibly make programs scriptable that only come with a captive user interface. When (you think) you need expect(1), that's a sign that something is wrong. It's the dressing for the wound after you or somebody else shot you in the foot. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message