This is the mail archive of the
mailing list for the Cygwin project.
Re: problem suspending "man bash" (intermittent)
On Wed, May 28, 2003 at 11:13:41AM -0400, Lev Bishop wrote:
> Windows XP home edition
> GNU bash, version 2.05b.0(9)-release (i686-pc-cygwin)
> cygwin dll version 1.3.22
> cygcheck -s -v -r attached
> So I have observed a strange phenomenon, where if I execute "man bash" in
> (using bash) and then suspend with ^Z, maybe one time in 4 there
> is a situation where the first keypress after the suspend still somehow
> gets sent to less rather than to the shell. Subsequently the shell works
> fine but when I "fg man" it only wants to draw the display a line at a
> time (ie it never refreshes the screen, even with ^L). Strangely, this
> behaviour happens much more frequently for "man bash" from xterm and not
> from the console, and even more strangely it seems much more likely to
> happen with the bash man page instead of others, though I have
> occasionally seen it with, eg, "man man". If you're looking to reproduce
> it, for me the best way is "man bash" from an xterm then repeatedly ^Z and
> "fg" until this happens (usually after 4 or 5 tries).
I tried reproducing this, but I don't get the same exact results. For
me, it takes 7 or 8 tries, and all I get is a missing '+ Stopped'
message from bash; the next keystrokes still go to bash, though. The
problem seems to go away if I use 'fg' instead of 'fg man'. I was not
It looks like some sort of race condition in the signal handling, but I
couldn't tell you where (cygwin, bash, less) it is. If you have access
to a Unix machine, it might be interesting to see if you can reproduce
this. Who knows, it might turn out to be a bash bug.
Dario Alcocer -- Sr. Software Developer, Helix Digital Inc.
firstname.lastname@example.org -- http://www.helixdigital.com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html