On Fri, Apr 10, 2009 at 14:58:16 -0400, Aron Griffis wrote: > [...] > I think the interesting part starts at line 9207, where bash (pid > 11715) writes some of the prompt. It's then interrupted by > SIGWINCH. On line 9218 it tries again, and on 9241 rxvt finishes > reading from bash. >
I've found some interesting entries in bash-4.0/CHANGES Between bash 3.2 and 4.0 - changes to readline: >>m. Fixed a bug that caused readline to reference uninitialized >> data structures if it received a SIGWINCH before >> completing initialzation. (this might be related to ctrl-c not working anymore, so it's a readline issue?) and Between bash-2.04-alpha1 and bash-2.04-beta1 (now that's a long time ago...) >>d. Fixes to the SIGWINCH code so that a multiple-line prompt >> with escape sequences is redrawn correctly. The problem(s) seem to be known in a way - and it seems bash-hackers think they are fixed. They probably didn't test their fixes with urxvt (and it's different SIGWINCH behaviour)? I think it's time to move the whole thing to the bash-bug mailinglist. Although the problem(s) manifest in urxvt, these are actually bash-issues. _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
