Re: broken CTRL-BREAK handling

[Christopher Faylor <cgf at redhat dot com>]

On Tue, Jul 17, 2001 at 02:50:42PM -0600, Troy Noble wrote:
>> Hmm.  I'll have to investigate this next week.  I can't easily retrieve
>> the B20 sources right now.
>
>I have the sources for b20.1 at my disposal too.  I will go look as
>well. Just for grins.
>
>> I think I recall that back in B20.1 days, people routinely
>> provided details rather than make vague assertions, too.
>
>Hmm... I have done that.  I know you get a lot of mail traffic, so
>I'll refresh your memory.

There is no more need to refresh my memory than there is to gratuitously
mention that there are supposed bugs in 1.x versions of cygwin that
aren't in B20.1.

What information is conveyed by making assertions like this?  What was
the intent beyond "yanking my chain"?

I understand that you have found what you consider to be bugs in the
interaction of cygwin with non-cygwin processes and I have expressed my
appreciation of the fact that you've submitted patches to attempt to
work around the problems.  I can appreciate that it is discouraging to
have your patches rejected but I'm sure you can appreciate my situation
also.  I'm not going to accept changes which I think are incorrect.  I
think I have explained why the patches are incorrect.

I still intend to investigate the CTRL-C issues that you mentioned at
some point.  It is on my list, if you don't come up with a patch.

>Here's the things I've reported thusfar:
>
>1. CTRL-C handling is broken with CYGWIN=notty in an emacs buffer.
>   I submitted patches for this already, in 5 different forms, each
>   of which fixed the problem in a different way.  I never did hit
>   on the right combination that you were looking for, and my
>   patches were rejected.  I gave up and patched my own copy from
>   the sources, and it's been working nicely for me for 2 months now.
>   All the other emacs users are still stuck though I suspect.
>2. CTRL-BREAK handling is broken, which I just reported and
>   mentioned a fix.  I patched my own copy of the DLL with this
>   as well, and it now behaves just like it did back in b20.1.
>
>The third, which I've not reported yet...

Ok, so, your "several" bugs is actually one previously reported problem,
one arguable bug reported today, and one problem that has, to the best
of my knowledge, never been reported by anyone else.

>At least my problems are getting fixed, but I'm having to do it
>all myself.  It's just unfortunate nobody else has gotten to take
>advantage of any fixes I've submitted yet.

Are you saying that I approved one of your patches and it hasn't been
applied?  I don't recall doing that.  If I have approved a patch and
have not applied it, then I apologize.  If you can point me to the URL
that contains the approval, I'll apply the patch.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/