On Fri, Jan 17, 2014 at 03:25:57PM +0000, Kevin Chadwick wrote: > Xterm gets stuck in a loop burning 100% cpu until you destroy it if you > do say. > > xterm -hold -e /bin/ls > > Might a patch based on this freebsd patch fix that? The second part of > it isn't in the xenocara tree. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=136686
Lots of code have changed in xterm since that bug report and fix. The second part is in xenocara, but OpenBSD doesn't define __FreeBSD__ so it's not used. Fixed. -- Matthieu Herrb
