From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-6146-mason-zsh=primenet.com.au@sunsite.auc.dk>
Received: (qmail 14230 invoked from network); 29 Apr 1999 05:14:45 -0000
Received: from sunsite.auc.dk (130.225.51.30)
  by ns1.primenet.com.au with SMTP; 29 Apr 1999 05:14:45 -0000
Received: (qmail 15928 invoked by alias); 29 Apr 1999 05:14:21 -0000
Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 6146
Received: (qmail 15921 invoked from network); 29 Apr 1999 05:14:20 -0000
Sender: gjb@cs.washington.edu
To: zsh-workers@math.gatech.edu
Subject: XTerm WaitForMap resource
From: Greg Badros <gjb@cs.washington.edu>
Date: 28 Apr 1999 22:14:15 -0700
Message-ID: <qrrk8uw3t5k.fsf@elwha.cs.washington.edu>
X-Mailer: Gnus v5.6.45/XEmacs 20.4 - "Emerald"

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:

echo "NXTerm*WaitForMap: false" | xrdb -merge
xterm -e zsh-3.0.5

The new xterm would come up with any of a number of errors when
executing some of the pipelines (involving awk, sed) in my .zshrc.


e.g.,

gawk: cmd. line:1: (FILENAME=- FNR=37) warning: error writing standard
output (Broken pipe)
/home/gjb/bin/share/path-remove-duplicates script failed; PATH may be
longer than needed
gawk: cmd. line:1: (FILENAME=- FNR=2) warning: error writing standard
output (Broken pipe)
....


I'm curious if anyone remembers fixing this problem and can explain what 
was going wrong and what the fix was.

Thanks,
Greg