public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Randy Galbraith <randy.galbraith@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: *shell* buffer freezes within Cygwin and Emacs 27.1
Date: Thu, 4 Feb 2021 09:54:28 -0700	[thread overview]
Message-ID: <CA+DxmavOA=0A7=XJL4eAPhk7Xr06_352=COSzMRCh8OH2zJhBA@mail.gmail.com> (raw)
In-Reply-To: <20210204090809.010b31c9b2a67cd4e33d69c2@nifty.ne.jp>

Good morning Takashi.

Thank you so much for your response. I just tried:

env CYGWIN=disable_pcon emacs-q

and cmd input/output works again. I'll now need to document this for our
team and seek out what this does.

Kind regards, -Randy


On Wed, Feb 3, 2021 at 5:08 PM Takashi Yano <takashi.yano@nifty.ne.jp>
wrote:

> On Wed, 3 Feb 2021 15:45:36 -0700
> Randy Galbraith via Cygwin <cygwin@cygwin.com> wrote:
> > Hi Everyone.
> >
> > Please note: I attempted to post this message from my work
> > email. I do not believe it every arrived.
> >
> > My long used work flow has recently stopped working. I'm trying to
> > understand why and how it could be resolved. The failing steps are:
> >
> > Cygwin64 Terminal (bash prompt)
> > startx -- :1 -multiwindow -clipboard &
> > xterm
> > emacs -q
> > M-x shell
> > $ cmd
> >
> > I expect to get a Windows 10 command prompt that works. Instead the shell
> > buffer display cmd output incorrectly formatted (e.g. extra white space)
> > and when I type a command like dir it freezes.
> >
> > I suspect this may be an issue related to a recent Windows 10 update
> > that in turn has changed the way cmd interacts with Cygwin bash and
> > Emacs. I have completed a re-install to the latest version (as of
> > 2/1/2021). Alas, this did not resolve the problem.
> >
> > ** details **
> > $ uname -r
> > 3.1.7(0.340/5/3)
> > GNU Emacs 27.1 (build 1, x86_64-pc-cygwin, GTK+ Version 3.22.28)
> > of 2020-10-29
> > ** details end **
> >
> > See below for *shell* buffer and cygcheck output.
> >
> > Kind regards,
> > -Randy Galbraith
> >
> > ** *shell* buffer **
> > ^[]0;~^G
> > xxxxxxxxx@xxxxxxxxxxx ~
> > $ cmd
> > <snip malformed output>
> >
> > $ Microsoft Windows [Version 10.0.17763.1697]
> > (c) 2018 Microsoft Corporation. All rights reserved.
> >
> > C:\cygwin64\home\xxxxxxxxx>dir
> > dir
> > ^ frozen at this point
> > ** *shell* buffer end **
>
> Please try latest cygwin snapshot.
> https://cygwin.com/snapshots/
>
> Or
> env CYGWIN=disable_pcon emacs -q
> instead of just
> emacs -q
>
> --
> Takashi Yano <takashi.yano@nifty.ne.jp>
>

  reply	other threads:[~2021-02-04 16:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 22:45 Randy Galbraith
2021-02-04  0:08 ` Takashi Yano
2021-02-04 16:54   ` Randy Galbraith [this message]
2021-02-04 17:23     ` Ken Brown
2021-02-04 20:26       ` Randy Galbraith

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='CA+DxmavOA=0A7=XJL4eAPhk7Xr06_352=COSzMRCh8OH2zJhBA@mail.gmail.com' \
    --to=randy.galbraith@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).