From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5560 invoked from network); 25 Nov 1999 18:21:44 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Nov 1999 18:21:44 -0000 Received: (qmail 23934 invoked by alias); 25 Nov 1999 18:21:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8781 Received: (qmail 23925 invoked from network); 25 Nov 1999 18:21:37 -0000 From: "Bart Schaefer" Message-Id: <991125182133.ZM6252@candle.brasslantern.com> Date: Thu, 25 Nov 1999 18:21:33 +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 makes it parsable for emacs's compile-goto-error Not that I particularly object to the change to zsh, but: (setq compilation-error-regexp-alist (append compilation-error-regexp-alist '(("^\\([^:]*\\): .*\\[\\([0-9]+\\)\\]" 1 2)))) -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com