From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-06.nifty.com (conssluserg-06.nifty.com [210.131.2.91]) by sourceware.org (Postfix) with ESMTPS id 43AE93851C36 for ; Thu, 21 Jan 2021 18:30:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 43AE93851C36 Received: from Express5800-S70 (x067108.dynamic.ppp.asahi-net.or.jp [122.249.67.108]) (authenticated) by conssluserg-06.nifty.com with ESMTP id 10LIUJJu004135 for ; Fri, 22 Jan 2021 03:30:20 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com 10LIUJJu004135 X-Nifty-SrcIP: [122.249.67.108] Date: Fri, 22 Jan 2021 03:30:23 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: Terminal output disappearing after SSH into cygwin Message-Id: <20210122033023.a1c813606ba51effca3629a4@nifty.ne.jp> In-Reply-To: <76e9ad7c-ee4e-4a91-e733-bcce51bcb134@cornell.edu> References: <644c7c45-b1a5-8c9f-8d6d-70b99a06c378@stefanist.com> <20210121221353.5eff1e02be701518f81fd3b8@nifty.ne.jp> <20210121222948.2e0044acb6d7475328f56ae2@nifty.ne.jp> <20210122022859.c58416aff3cbfe5c8d3eece8@nifty.ne.jp> <76e9ad7c-ee4e-4a91-e733-bcce51bcb134@cornell.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2021 18:30:37 -0000 On Thu, 21 Jan 2021 13:13:56 -0500 Ken Brown wrote: > # when leaving the console clear the screen to increase privacy > if [ "$SHLVL" = 1 ]; then > [ -x /usr/bin/clear ] && /usr/bin/clear > fi That should be the culprit. Is editing /etc/bash.bash_logout the right thing? -- Takashi Yano