This sounds very much like a bug in zsh. "interrupt" sounds like write()
received an EINTR, and zsh didn't retry as it should have.
The EINTR is likely the result of the SIGWINCH signal that urxvt (or the
kernel, depending on window manager behaviour) sends, which would explain
why it is a race and doesn't always happen.
I am just speculating of course - an strace of zsh when the problem
happens would give good evidence for that.
However, it's probably easier to see if zsh properly retries interrupted
syscalls in print, and if not, whether fixing zsh would make the problem
go away.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
