From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26305 invoked from network); 23 Feb 2006 01:08:48 -0000 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,FORGED_RCVD_HELO autolearn=ham version=3.1.0 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 23 Feb 2006 01:08:48 -0000 Received: (qmail 45551 invoked from network); 23 Feb 2006 01:08:40 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 23 Feb 2006 01:08:40 -0000 Received: (qmail 28886 invoked by alias); 23 Feb 2006 01:08:32 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9959 Received: (qmail 28876 invoked from network); 23 Feb 2006 01:08:32 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 23 Feb 2006 01:08:32 -0000 Received: (qmail 44300 invoked from network); 23 Feb 2006 01:08:32 -0000 Received: from mta1.prod1.dngr.net (HELO mfe1.prod.danger.com) (216.220.209.220) by a.mx.sunsite.dk with SMTP; 23 Feb 2006 01:08:29 -0000 Received: from [10.253.10.252] (HELO localhost.localdomain) by mfe1.prod.danger.com (CommuniGate Pro SMTP 4.1.6) with ESMTP id 553816851 for zsh-users@sunsite.dk; Wed, 22 Feb 2006 17:08:26 -0800 Date: Wed, 22 Feb 2006 17:08:24 -0800 Subject: Re: a.out output not displayed X-Mailer: Danger Service X-Danger-Send-Id: AABfd0P9CwoAAYbN Content-Transfer-Encoding: 7bit In-Reply-To: <20060223004357.GB793@prunille.vinc17.org> Content-Type: text/plain; charset="us-ascii"; format="flowed" To: zsh-users@sunsite.dk Mime-Version: 1.0 References: <43FCE62C.2010804@ece.gatech.edu> <20060223004357.GB793@prunille.vinc17.org> From: Barton Schaefer Message-Id: <1140656906.385CB496@fc9.dngr.org> On Wed, 22 Feb 2006 4:51pm, Vincent Lefevre wrote: >> setopt no_prompt_cr > > Which is bad. The best solution is to use a recent zsh version > (4.3.0-dev-5 or wait for 4.3.1). Or look at a recent copy of the zsh FAQ, which explains how users of older versions can employ the fix that's built in to upcoming version.