X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=R+F75MQXjSKe8NE8 6qiqm0cyJDtBoe9oyjp7EOtX7EmmtkDjMBSyIq+09hN6KhIa2Wo7Cc/ZHwMkNgAC xIEDEc8XjPWKGw+MiJkhE5RfRtKD85R8QGGZMyJXDDiLInlz5tgmu1H9Qc88hg/z kBmL2tFGo0m0vMgwQY/KUsiepp4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:cc:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=S17LwjMkByFKH7EhlX8MY6 Hdzi0=; b=EZxGc2rJMNINq592EId3Mv7HJKhOcjqN6/od7oifz35GRinvr16mIc jfY0NFuU7nn67zQGfcbDlmiqXgV3BMroEuQtTr8t39bi3iHV4jDE8/SgwedcX4Cg zXaF79wHB4I7BmRFu24mGRCdU2vj2WORJKdmQoYKlRsNP7iwm0m44= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-7.3 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,KAM_ASCII_DIVIDERS,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=Cygwin, row, emacs, screen X-HELO: atfriesa01.ssi-schaefer.com Subject: Re: [ANNOUNCEMENT] cygwin 3.1.0-0.6 (TEST) To: cygwin AT cygwin DOT com References:

<20191011182439 DOT 6dd3fedb2c7138627e53c053 AT nifty DOT ne DOT jp> Cc: Takashi Yano From: Michael Haubenwallner Openpgp: preference=signencrypt Message-ID: <99298a9a-5de3-0e14-0128-c693b278f5e7@ssi-schaefer.com> Date: Mon, 14 Oct 2019 13:07:22 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20191011182439.6dd3fedb2c7138627e53c053@nifty.ne.jp> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 10/11/19 11:24 AM, Takashi Yano wrote: > 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 > 3) Execute cmd.exe. Well... even that one is counter intuitive regarding the 'Last login' line. After login into Cygwin sshd, the 'Last login' line is not shown: haubi AT linuxbox ~ $ ssh cygwin2019 ---------------------------------------- > > haubi AT cygwin2019 ~ > $ > > > > > > > ---------------------------------------- When starting cmd, the terminal does loose colors, and the 'Last login' line suddenly is shown as first line: ---------------------------------------- > Last login: Mon Oct 14 12:30:52 2019 from 192.168.56.1 > > haubi AT cygwin2019 ~ > $ cmd > Microsoft Windows [Version 10.0.17763.805] > (c) 2018 Microsoft Corporation. All rights reserved. > > C:\cygwin64\home\haubi> > > ---------------------------------------- However, with TERM=dumb, the terminal content is: ---------------------------------------- > {some output from previous linux commands} > {some output} > {some output} > {some output} > {some output} > haubi AT linuxbox ~ $ TERM=dumb ssh cygwin2019 > Last login: Mon Oct 14 12:37:24 2019 from 192.168.56.1 > > haubi AT cygwin2019 ~ > $ ---------------------------------------- And when cmd was started: ---------------------------------------- > Last login: Mon Oct 14 12:37:24 2019 from 192.168.56.1 > > haubi AT cygwin2019 ~ > $ cmd > Microsoft Windows [Version 10.0.17763.805] > (c) 2018 Microsoft Corporation. All rights reserved. > > C:\cygwin64\home\haubi> > > ---------------------------------------- Actually I do prefer the TERM=dumb behaviour, having the current terminal buffer content get redrawn at line 1 when cmd is started only, not when running just Cygwin programs. My real problem is more sophisticated, and boils down to the creation of some pty's in a row, each having some commands run inside, and I do expect to see the output of each command while the series runs and when done, much like: ---------------------------------------- > {some output from previous linux commands} > {some output} > {some output} > haubi AT linuxbox ~ $ ssh -t cygwin2016 hostname; hostname; ssh -t cygwin2016 hostname > cygwin2016 > Connection to cygwin2016 closed. > linuxbox > cygwin2016 > Connection to cygwin2016 closed. > haubi AT linuxbox ~ $ ---------------------------------------- And looking at the code actually makes me belive that even emacs does have troubles when the clear screen code is emitted on pty creation... Thanks! /haubi/ (in hope that "embedding the screen shots" does work) -- 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