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: Wed, 18 Mar 2020 06:44:37 -0700 [thread overview]
Message-ID: <CAA5t8VqGezsKs5z4RGmYk=xNpWhAMdH+CSZ-Ac+i1crYfzZvAA@mail.gmail.com> (raw)
In-Reply-To: <77d22efc-4a2c-422a-c7d5-22b5632e707d@cornell.edu>
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.
On Tue, Mar 17, 2020 at 6:04 PM Ken Brown via Cygwin <cygwin@cygwin.com>
wrote:
> On 3/17/2020 7:14 PM, David Karr via Cygwin wrote:
> > Yesterday I upgraded Cygwin, which I hadn't done in a while. I had
> recently
> > upgraded my Windows 10 OS from build 1709 to 1809 (yes, those are
> correct).
> >
> > My current Emacs version is 26.3, but I don't know what it was before the
> > upgrade.
> >
> > If I create a shell buffer and execute a command that produces plain,
> > uncolored output, it appears to work fine. However, output from "Maven"
> > has always been colorized for me, and it's always worked fine. Today,
> I'm
> > seeing that the output is severely corrupted. If I pipe the output into
> a
> > file and view that, which doesn't have colors, the contents are fine. I
> > also ran the same process in a mintty window, which is colorized in the
> > same way, and that is also working fine.
> >
> > For instance, if this is what I see in a mintty buffer:
> > -----------------------
> > [WACDTL03DK068X:~/git/cartms] mvn package
> > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
> > MaxPermSize=128m; sup
> > port was removed in 8.0
> > [INFO] Scanning for projects...
> > [WARNING]
> > ...
> > -------------------------
> >
> > What I see in the Emacs shell buffer is something like this:
> > -------------------------
> > [WACDTL03DK068X:~/git/cartms] mvn package
> > [WACDTL03DK068X:~/git/cartms] [WACDTL03DK068X:~/git/cartms] Java
> > HotSpot(TM) 64-
> > Bit Server VM warning:ignoring option MaxPermSize=128m; support was
> removed
> > in
> > 8.0
> > [INFO] Scanning for projects...[
> > [WARNING] l
> >
> >
> >
> >
> >
> > ....
> > ---------------------------
> >
> > The first thing I see is that it prints the shell prompt twice AFTER
> > pressing enter on the command line to run. That might possibly be an
> issue
> > with my Bash dot files, but this didn't happen before the Cygwin upgrade,
> > and it doesn't happen in the mintty window.
> >
> > After that, it gets even worse. The "Java HotSpot ..." line prints in
> > three lines, instead of a single line. Then, the first "WARNING" line
> has
> > the "l" at the end of the line, and then numerous blank lines. The rest
> of
> > the output is mangled in other ways.
> >
> > Any ideas what might be wrong here?
>
> This is probably related to the new pty code. Does it help if you start
> emacs
> like this?
>
> CYGWIN=disable_pcon emacs
>
> If so, that confirms my guess and gives you a workaround.
>
> Ken
> --
> Problem reports: https://cygwin.com/problems.html
> FAQ: https://cygwin.com/faq/
> Documentation: https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>
next prev parent reply other threads:[~2020-03-18 13:44 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 [this message]
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
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='CAA5t8VqGezsKs5z4RGmYk=xNpWhAMdH+CSZ-Ac+i1crYfzZvAA@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).