From: m0viefreak <m0viefreak.cm@googlemail.com>
To: cygwin@cygwin.com
Subject: 3.1.x: Mangled input/output when calling non-cygwin programs
Date: Sat, 01 Feb 2020 18:00:00 -0000 [thread overview]
Message-ID: <7e3d947e-b178-30a3-589f-b48e6003fbb3@googlemail.com> (raw)
Hi,
Since Cygwin 3.1's pseudo console support was introduced I've run into
lots of issues with non-cygwin programs.
1) Mangled output: See screenshot [1].
As you can see, at what it seems random places, the output is broken.
The above can easily be reproduced using Apache Maven in any project,
e.g. using a sample project created using [2].
2) Terminal width: For some reason, non-native programs do not use the
full width of the terminal (Mintty and TERM=xterm-256color). Can also
be seen in [1] (blue highlight) and reproduced e.g. using Maven with
a relatively small window.
3) Typed characters while non-cygwin program is running are lost.
Usually, when typing characters while a native program executes,
which does *not* read from standard input, after the program exits,
all these typed characters are put into the prompt.
When executing a non-native program, such as, again, "mvn clean",
which does not read from stdin, typed characters are completely lost.
This is very frustrating, since I am often quicker at tying the
next command, while the previous command is still doing something.
4) Importance of TERM: When connecting to my Cygwin installation using
SSH using Putty, TERM=putty-256color is set. When executing non-
native program from that session using that TERM, output is broken
even worse than in 1), and also keybindings are broken. I need to
force TERM=xterm-256color for those invocations.
Shouldn't this be handled transparently and enforced automatically by
the pcon code?
Note 1: This is tested using the latest Snapshot 2020-01-31 18:10:26 UTC
from https://cygwin.com/snapshots/.
Note 2: It seems that the problems can be solved by setting
CYGWIN=disable_pcon but it feels like there is some bug in the
PTY code (not in the non-native program being called).
[1] https://images2.imgbox.com/dc/2d/MQwSH9S4_o.png
[2]
http://maven.apache.org/guides/getting-started/index.html#How_do_I_make_my_first_Maven_project
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2020-02-01 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 18:00 m0viefreak [this message]
2020-02-02 9:59 ` Takashi Yano
2020-02-02 12:18 ` m0viefreak
2020-02-02 19:01 ` Takashi Yano
2020-02-03 14:20 ` Takashi Yano
2020-02-09 13:42 ` Takashi Yano
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=7e3d947e-b178-30a3-589f-b48e6003fbb3@googlemail.com \
--to=m0viefreak.cm@googlemail.com \
--cc=cygwin@cygwin.com \
/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).