From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5408 invoked from network); 25 Nov 1999 17:58:25 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Nov 1999 17:58:25 -0000 Received: (qmail 21523 invoked by alias); 25 Nov 1999 17:58:20 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8780 Received: (qmail 21514 invoked from network); 25 Nov 1999 17:58:18 -0000 From: "Bart Schaefer" Message-Id: <991125175814.ZM6178@candle.brasslantern.com> Date: Thu, 25 Nov 1999 17:58:14 +0000 In-Reply-To: <19991125122020.B11876@dman.com> Comments: In reply to Clint Adams "PATCH: make zsh print errors like a well-behaved compiler" (Nov 25, 12:20pm) References: <19991125122020.B11876@dman.com> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: make zsh print errors like a well-behaved compiler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Nov 25, 12:20pm, Clint Adams wrote: } Subject: PATCH: make zsh print errors like a well-behaved compiler } } This will change the error given when running a script I've actually been wondering whether this sort of thing should be configurable (PS5, anyone?). In some circumstances one might not want line numbers at all; in fact, in some cases one might rather see badcommand: command not found instead of scriptname: command not found: badcommand -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com