public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Houder" <houder@xs4all.nl>
To: cygwin@cygwin.com, "Thomas Wolff" <towo@towo.net>
Subject: Re: SIGINT generated by Control-C, is not delivered in mintty
Date: Tue, 21 Jul 2015 21:32:00 -0000	[thread overview]
Message-ID: <6aafae9d14844a1ae2095f74dd4e42e1.squirrel@oude-webmail.xs4all.nl> (raw)
In-Reply-To: <55AE6BCB.5@towo.net>

>> You are the expert on mintty now ... I only observed a "pattern":
> let's say maintainer... expert on terminal issues maybe, but not on
> Windows API and specifics of POSIX process control...

Language, language, Henri!

Hi Thomas,

1. Re. "You are the expert on mintty now ..."

First of all, my apologies ... I should have accompanied my statement with a Smiley ( :-) )

You are not an export on mintty yet ... I am aware of that (as we all are). You cannot be an
expert on mintty within a couple of weeks/months ...

I only wanted to 'signal', that my knowledge of mintty, compared to yours, is nill.

Furthermore, I wanted to point out exactly when mintty "failed" ...

2. priority of the bug

Secondly, my first reason for interfering with this thread was, that I wanted to have a clear
understanding of the problem ...
Next, I presented a work-around, as you did:

 1. cmd /c <root>/bin/mintty -- mine
 2. setsid mintty -- yours
 3. run mintty -- in case the "bash window" should close itself
 4. etc.

What I mean is, that I do not believe there is a serious problem with mintty (meaning, you can
afford yourself some time in finding a solution).

But, of course, that is my opinion.

3. Re. "Windows API and specifics of POSIX process control ..."

Third, I hear you ... but I am afraid that your only point of reference here is Corinna V. Only
she (sadly enough) has the intimate knowledge in this area (ever since Christopher Faylor left).
(something that should freak out the community and her boss)

... Perhaps she ...

> I've implemented a tweak that should resolve the issue. Please try
> https://github.com/mintty/mintty/archive/master.zip

A tarball? I may have a stab at it ... but it has been a long time since I compiled anything
related to Cygwin ...

> I think it's a workaround rather than a fix though as I think the actual
> problem is within cygwin.

I heard you the first time. However, Cygwin (yes, the part that Corinna V. knows all about) may
have been modified for justifiable reasons. And in that case, mintty has to adapt.

Bottom-line: allow yourself more time studying mintty (to me there is not really a problem with
mintty).

Good night!

Henri

=====



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-07-21 21:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  7:44 Ronald Fischer
2015-07-14  9:28 ` Achim Gratz
2015-07-15  8:24   ` Ronald Fischer
2015-07-18 22:57   ` Thomas Wolff
2015-07-15  8:47 ` Marco Atzeri
2015-07-15 14:40   ` Thomas Wolff
     [not found] ` <55A9517A.5090308@towo.net>
2015-07-20 10:59   ` Ronald Fischer
2015-07-20 12:16     ` Houder
2015-07-20 12:50       ` Ronald Fischer
2015-07-20 13:40         ` Houder
2015-07-20 13:50           ` Ronald Fischer
2015-07-20 19:38           ` Thomas Wolff
2015-07-21  8:45             ` Houder
2015-07-21 15:57               ` Thomas Wolff
2015-07-21 21:32                 ` Houder [this message]
2015-07-19 12:56 Houder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6aafae9d14844a1ae2095f74dd4e42e1.squirrel@oude-webmail.xs4all.nl \
    --to=houder@xs4all.nl \
    --cc=cygwin@cygwin.com \
    --cc=towo@towo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).