public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Michael Haubenwallner <michael.haubenwallner@ssi-schaefer.com>
Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST)
Date: Fri, 11 Oct 2019 09:25:00 -0000	[thread overview]
Message-ID: <20191011182439.6dd3fedb2c7138627e53c053@nifty.ne.jp> (raw)
In-Reply-To: <aa4429ee-a974-5888-f602-d2e686f8cc2b@ssi-schaefer.com>

Hi Michael,

On Thu, 10 Oct 2019 12:43:56 +0200
Michael Haubenwallner wrote:
> I'm encountering another strange behaviour I do not remember to have seen before:
> 
> Using ssh from some Linux xterm into the Cygwin sshd running on Server 2019
> does clear the current terminal content as if /usr/bin/clear was executed.

This is intentional behaviour.

The pseudo console has its own screen buffer behind, and redraws
the screen based on the screen buffer at undetermined timing.
The screen buffer is empty at the beginning, so the screen should
be cleared at the opening of the pty so that the real screen and
the screen buffer are synchronozed.

The clear screen is prevented when TERM=dumb, so you can see what
happens if clear screen is not done by following steps.

1)  Execute ls or ps to draw something to screen.
2) env TERM=dumb ssh <cygwin-hostname>
3) Execute cmd.exe.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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

  reply	other threads:[~2019-10-11  9:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22 16:24 Ken Brown
2019-09-24  7:38 ` Michael Haubenwallner
2019-09-24 12:50   ` Ken Brown
2019-09-24 23:05 ` Ken Brown
2019-09-25 18:30   ` Takashi Yano
2019-09-26 12:51     ` Takashi Yano
2019-09-26 14:38       ` Ken Brown
2019-10-02 14:04 ` Michael Haubenwallner
2019-10-02 18:24   ` Ken Brown
2019-10-03 10:44   ` Takashi Yano
2019-10-10 10:44 ` Michael Haubenwallner
2019-10-11  9:25   ` Takashi Yano [this message]
2019-10-14 11:07     ` Michael Haubenwallner
2019-10-16 12:32       ` Takashi Yano
2019-10-18 11:36         ` Takashi Yano
2019-10-16 14:34       ` Takashi Yano
2019-10-16 16:34         ` Michael Haubenwallner

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=20191011182439.6dd3fedb2c7138627e53c053@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=michael.haubenwallner@ssi-schaefer.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).