This is the mail archive of the
mailing list for the Cygwin project.
Re: once more unto the breech - please try a snapshot so I can release this thing
On Wed, Jan 11, 2006 at 10:41:20PM -0800, Yitzchak Scott-Thoennes wrote:
> On Wed, Jan 11, 2006 at 08:17:08PM -0500, Christopher Faylor wrote:
> > On Wed, Jan 11, 2006 at 10:35:37AM -0800, Yitzchak Scott-Thoennes wrote:
> > >On Tue, Jan 10, 2006 at 09:23:41PM -0500, Christopher Faylor wrote:
> > >> I hope that I've nailed down the last of the problems due to trying to
> > >> hide the console, aka ssh doesn't work, aka emacs doesn't work, aka
> > >> rxvt doesn't work, aka setsid something doesn't work.
> > >
> > >:( emacs doesn't work.
> > >
> > >Twice now with the 20060110 13:32:19 snapshot, I've had it no longer
> > >receive Ctrl-C's (running emacs from mutt from a cygwin.bat window).
> > >Doesn't happen consistently, but when it does, it persists in any
> > >emacs started in that window. When I finally exit bash, cmd.exe gives
> > >a Terminate batch job (Y/N)? prompt.
> > >
> > >Probably useless information: I had something similar happen once
> > >with, I think, the 20060105 snapshot, but then cygwin1.dll showed some
> > >error message (TM) about a minute after Ctrl-C was pressed.
> > I notice that you included the part of my message where I say what
> > I think I fixed but didn't include the part where I mentioned that
> > we need to know the steps to duplicate the problem.
> > What *exactly* are you doing? I think it's been mentioned a few times
> > that neither Corinna nor I use emacs so "running emacs from mutt"
> > doesn't mean a lot to me and it probably doesn't mean much to the
> > only other person who's going to be interested in tracking down
> > this problem.
> Usually using mutt's g command to reply to an email, which starts e.g.
> emacs -nw /tmp/mutt-DHX98431-3796-19
> to edit an email. And when I've finished editing, I use the Ctrl-X
> Ctrl-C command to exit, and sometimes the Ctrl-X is registered but the
> Ctrl-C is ignored. And sometimes it works. What the difference is,
> I don't know. I've had it happen one more time, and still have the
> window open.
> Just now, I tried entering sleep 20 at the bash prompt in that window
> and right thereafter Ctrl-C and the sleep wasn't interrupted.
> Sorry I can't tell you what makes this happen or not happen.
Just in case it's relevant, note that I have experimental bash,
readline, libreadline6, findutils, and coreutils.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html