SO I have been poking around some more and I can report some more details.
I can say that it doesn't seem to be a problem with man, bash or less, and
rather seems to be a problem concerning the way cygwin sends signals to a
pipeline. The reason it showed up with man bash rather than others is
On Thu, May 29, 2003 at 11:02:59PM -0400, Lev Bishop wrote:
Here follow detailed results of my experimenting.
Send the manpage to a file:
$ man bash mb
Use less to look at it:
$ less mb
No problems suspending/restarting.
Use a pipeline in a subshell to view it (the way man does it):
$
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
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
On Thu, May 29, 2003 at 05:04:26AM -0700, Dario Alcocer wrote:
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 '[1]+ Stopped'
message from bash; the next keystrokes still go to bash, though. The
problem seems to go
5 matches
Mail list logo
