On Sun, Apr 12, 2009 at 06:50:23PM +0200, Jukka Salmi <[email protected]>
wrote:
> > can see whether bash really writes the prompt or indeed bash just doesn't
> > write the prompt.
>
> Sure, see below. Bash receives SIGWINCH after having written the first
Thanks, perfectly caught.
> (The last read(2) shown above successfully reads the first character (#)
> of the command I entered after the prompt was (incorrectly) printed.)
>
> Moving to bug-bash now... ;-)
Maybe the fix is as simple as blocking sigwinch when bash tries to write
the prompt, plus some flag yada yada. Ok, maybe not so simple :)
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
