setup and mintty (was Re: New setup.exe release?)

Charles Wilson
Mon May 23 18:16:00 GMT 2011

On 5/23/2011 1:25 PM, Christopher Faylor wrote:
> Maybe we should be looking into introducing a way to set the CYGWIN
> environment variable in the global environment and adding c:\cygwin\bin
> (or whatever) to the global PATH as well.

I disagree.  I deliberately keep cygwin paths out of my global PATH, so
that I can switch between various separate cygwin installs, and various
MinGW/MSYS installs, without them all conflicting with each other.

If we DO change setup to muck with global %PATH%, then we need another
checkbox to opt out.  (BTW, whatever happened to that 'check box
persistence' patch?)

> But, I am extemely in favor of making mintty the default terminal.  It
> would present a much nicer end-user experience out-of-the-box even if
> some pty stuff doesn't work quite right.

Oh, sure, I'm not against that. I specifically said #5 was fine with me:
  5) or punt.  Who needs linedraw anyway.
which was my way of saying: sure, go ahead and make mintty the default.
If we really care about linedraw, we can fix it later -- and I wonder if
we really DO care about it.  It sounds like the consensus here is: we
don't care /much/, but PTC...

And that's fine.

> And, I can just imagine the blog entries now: "Cygwin finally offers an
> intelligent terminal interface - after ten years!"

Yep, that + unicode support is the most obvious user-visible improvement
in the 'new user experience' in a long time.  Maybe even since the
hallowed B19 -> B20.1 transition </cue choirs of angels>.

Most of the other great improvements aren't immediately obvious to the
new user...

> The only downside that I see is that Andy may ask to renegotiate his
> contract.  I wouldn't be surprised if he asked to be paid double what
> he's getting now, in fact.

Andy needs a tipjar -- and a plug on this page:


More information about the Cygwin-apps mailing list