From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22027 invoked from network); 29 Apr 1999 15:30:38 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 29 Apr 1999 15:30:38 -0000 Received: (qmail 6996 invoked by alias); 29 Apr 1999 15:30:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6155 Received: (qmail 6987 invoked from network); 29 Apr 1999 15:30:25 -0000 From: "Bart Schaefer" Message-Id: <990429083013.ZM8225@candle.brasslantern.com> Date: Thu, 29 Apr 1999 08:30:13 -0700 In-Reply-To: Comments: In reply to Greg Badros "XTerm WaitForMap resource" (Apr 28, 10:14pm) References: X-Mailer: Z-Mail (4.0b.820 20aug96) To: Greg Badros , zsh-workers@math.gatech.edu Subject: Re: XTerm WaitForMap resource MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Apr 28, 10:14pm, Greg Badros wrote: } Subject: XTerm WaitForMap resource } } It appears that Zsh-3.0.6 has fixed a bug I noticed in zsh-3.0.5 whereby } if the zsh exec'd before the xterm (nxterm in my case) mapped, it would } get confused: } } I'm curious if anyone remembers fixing this problem and can explain what } was going wrong and what the fix was. I'm pretty sure it's this one: 1998-10-24 19:48 Bart Schaefer * Src/exec.c: Patch readoutput() so the output of command substitutions isn't lost on an EINTR read error. A SIGWINCH would be sent when the xterm mapped itself, and if a $(...) happened to be running at that moment, the output would simply vanish. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com