From: David Karr <davidmichaelkarr@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: After cygwin upgrade, Emacs shell buffers with colors are corrupted
Date: Thu, 19 Mar 2020 12:50:36 -0700 [thread overview]
Message-ID: <CAA5t8Vp2x-3-TKqWq=tq2TLN_oCLXuBicvPQE+NLpU9tEEHQCA@mail.gmail.com> (raw)
In-Reply-To: <CAA5t8VpfWz8zeg5_O3=AwDHaUj2TBQMejFTV8Dcu9bPA8B_58g@mail.gmail.com>
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.
next prev parent reply other threads:[~2020-03-19 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 23:14 David Karr
2020-03-18 1:03 ` Ken Brown
2020-03-18 13:44 ` David Karr
2020-03-18 15:22 ` Andrey Repin
2020-03-18 16:35 ` Ken Brown
2020-03-18 21:17 ` David Karr
2020-03-19 19:50 ` David Karr [this message]
2020-03-19 19:59 ` William M. (Mike) Miller
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='CAA5t8Vp2x-3-TKqWq=tq2TLN_oCLXuBicvPQE+NLpU9tEEHQCA@mail.gmail.com' \
--to=davidmichaelkarr@gmail.com \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).