Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: XTerm WaitForMap resource
- X-seq: zsh-workers 6155
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Greg Badros <gjb@xxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: XTerm WaitForMap resource
- Date: Thu, 29 Apr 1999 08:30:13 -0700
- In-reply-to: <qrrk8uw3t5k.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <qrrk8uw3t5k.fsf@xxxxxxxxxxxxxxxxxxxxxxx>
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@xxxxxxx>
* 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author