From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: pseudo console and auto-wrap
Date: Fri, 06 Mar 2020 20:41:00 -0000 [thread overview]
Message-ID: <CANV9t=RVqXc47uzCb0GUiZKxAx-tGHxD5qM2adv7bnZ486tWsA@mail.gmail.com> (raw)
In-Reply-To: <20200306005122.52a9b50615a16546e60defc1@nifty.ne.jp>
On Thu, Mar 5, 2020 at 8:52 AM Takashi Yano wrote:
> Thomas Wolff wrote:
> > With ConPTY support, the following command results in output that
> > contains an explicit newline at the auto-wrap position:
> > cmd /c echo a line which is wider than your terminal ...
> >
> > For copy/paste, this is surprising and undesired
> > (https://github.com/mintty/mintty/issues/971).
> > Can the line wrapping case be handled specifically, assuming proper
> > auto-wrap mode on the terminal side, to avoid this?
>
> This is internal behaviour of pseudo console.
> So we can not touch it. WSL also behaves the same.
Observations when I ssh to a Windows 10 1909 machine running cygwin
3.1.4/OpenSSH 8.2...
I ran ssh-host-config and tested both with disable_pcon set in CYGWIN
environment variable and without. (This sets REG_SZ value
HKLM\SYSTEM\CurrentControlSet\Services\cygsshd\Parameters\Environment\CYGWIN=disable_pcon)
With disable_pcon set:
echo "$PATH" -- wraps correctly
cmd /c echo %PATH% -- wraps correctly
winpty cmd /c echo %PATH% -- wrapping broken
Without disable_pcon set:
echo "$PATH" -- wraps correctly
cmd /c echo %PATH% -- wrapping broken
winpty cmd /c echo %PATH% -- wrapping broken
I would note that in both cases, winpty output is not correct.
Does anyone have any ideas on how to fix it?
Thanks,
Bill
--
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 prev parent reply other threads:[~2020-03-06 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 13:04 Thomas Wolff
2020-03-06 12:55 ` Takashi Yano
2020-03-06 20:41 ` Bill Stewart [this message]
[not found] ` <aaf835fc-8b8b-f67d-ec42-79b39d0026ef@towo.net>
2020-03-10 20:36 ` Brian Inglis
2020-04-01 21:55 ` Thomas Wolff
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='CANV9t=RVqXc47uzCb0GUiZKxAx-tGHxD5qM2adv7bnZ486tWsA@mail.gmail.com' \
--to=bstewart@iname.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).