Marc Lehmann wrote: [Wed Apr 08 2009, 11:14:25PM EDT] > What you describe really looks like a bug in bash - most likely, it tries > to write the prompt, for some reason it gets cut into two parts (likely > due to the two lines - linux suffers from similar idiocies in it's ttys), > and when your shell gets a SIGWINCH it forgets to print the rest of the > prompt.
Or in my case, it actually gets printed twice. See http://agriffis.n01se.net/misc/urxvtc-bash-prompt.png > While this all could still be some problem in urxvt, a bash bug fits the > description much better at the moment. Agreed. > Maybe you would be able to reproduce this under ktrace (on bash), so one > can see whether bash really writes the prompt or indeed bash just doesn't > write the prompt. A ktrace on urxvt would show whether it correctly > configures the pty, too. I'll try to do this soon. I attempted once earlier and found the tracing interfered enough that the race didn't appear. Aron _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
