please see [1]. downgrading to 1.0.3 reverts the problem. no solution so far. [1]: http://forums.gentoo.org/viewtopic-t-795560-highlight-.html Reproducible: Always Steps to Reproduce:
Created attachment 206074 [details] emerge --info emerge --info
which version of xterm are you using? Please explain your problem here again.
from f.g.o.: i just noticed that my xterms do not close any more when i hit "exit" or "^D". the option that causes this is "-lc". without that (or with "+lc") it works fine. what happens is that x11-apps/luit is called. downgrading luit from 1.0.4 to 1.0.3 solves the problem. i am currently running xterm-249, but tried 243 too, same result.
That's a known defect which I fixed in my alternate version of luit: 2009/8/16 - reset connection to blocking mode on exit. modify poll-flavor of waitForInput to also check if the connection has hung up. (It's a defect introduced by xorg changes in April 2009).
fwiw - the changelog is here: http://invisible-island.net/luit/luit.log.html
ok. but what does that mean ? when will this fix appear in the portage tree ?
I don't know - perhaps xorg will fix it sometime.
fwiw - http://lists.freedesktop.org/archives/xorg/2009-April/045022.html
Thomas, Could you send the patch to the xorg-devel mailing list? Let's try to merge back your fork and the xorg one, seems like a good central place for collaboration. Thanks
The proper place for discussing that would be on the xorg list. I pointed to that thread, to give some context.
Could anyone who actually uses luit file a bug upstream [1] so that they actually get notified of the bug? @Thomas, I don't know what the discussion should be about, everyone seems to be using the Xorg fork of luit. So it's rather whether you want to keep maintaining your own version or not. I have commit access to fd.o, so if you provide patches to the mailing list, I'll gladly commit them once they are ACKed. Thanks [1] https://bugs.freedesktop.org
after a year: ping :)
"Aside from that (and some cosmetic changes to C source, as well as providing a different configure script), and omitting this change-log, the xorg 1.1.0 is the same as the 2010/6/1 version." And I can't reproduce this bug anymore with xterm-270 and luit-1.1.0 so assuming this one is fixed now.