XTerm WaitForMap resource

XTerm WaitForMap resource

[Greg Badros]

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

Re: XTerm WaitForMap resource

[Bart Schaefer]

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 <schaefer@zsh.org>

	* 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