After cygwin upgrade, Emacs shell buffers with colors are corrupted

[William M. (Mike) Miller]

On Thu, Mar 19, 2020 at 3:51 PM David Karr via Cygwin <cygwin@cygwin.com>
wrote:

> On Wed, Mar 18, 2020 at 2:17 PM David Karr <> wrote:
>
> > On Wed, Mar 18, 2020 at 9:38 AM Ken Brown via Cygwin <> wrote:
> >
> >> On 3/18/2020 11:22 AM, Andrey Repin wrote:
> >> > Greetings, David Karr!
> >> >
> >> >> Thanks, that worked.  For now, I guess I have to figure out how to
> set
> >> that
> >> >> property permanently, or until this pty bug is fixed.. I start Emacs
> >> from a
> >> >> shortcut, executing "emacs.xml".  I see the file appears to have some
> >> >> syntax for setting the environment, but I've never inspected that
> file
> >> >> before.
> >> >
> >> > You set it in Windows.
> >>
> >> Not necessarily.  He might just want to set it for emacs.  Editing
> >> emacs.xml is
> >> a fine way to do it.
> >>
> >
> > I have no idea whether I would want to do it only for Emacs, as I don't
> > know what the issue is.
> >
> > However, if I wanted to, could you point me to the documentation for
> > changing that file?  The README doesn't say anything about this.
> >
> >
> Just so it's clear, Ken Brown directly sent me some information of what he
> knew about the emacs.xml documentation, but it didn't appear to work.
>
> I've verified that setting the CYGWIN variable globally to "disable_pcon"
> has resolved the problem.
>

This is what I did as well to address the problem of M-x gdb not working in
emacs in a new Cygwin installation. I don't know what I might be losing in
other functionality by setting the CYGWIN environment variable globally to
"disable_pcon", but it did address my gdb issue effectively.

-- 
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com