X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 54687385801D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca X-Authority-Analysis: v=2.4 cv=Yq/K+6UX c=1 sm=1 tr=0 ts=600a89d2 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 To: cygwin AT cygwin DOT com References: <644c7c45-b1a5-8c9f-8d6d-70b99a06c378 AT stefanist DOT com> <9072877f-c67d-5767-7a58-274abecfecbf AT stefanist DOT com> <190171158 DOT 2668557 DOT 1611244936009 AT mail DOT yahoo DOT com> From: Brian Inglis Organization: Systematic Software Subject: Re: Terminal output disappearing after SSH into cygwin Message-ID: <9a0ce80d-fcdb-9f07-788c-c157a2de8535@SystematicSw.ab.ca> Date: Fri, 22 Jan 2021 01:16:17 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <190171158.2668557.1611244936009@mail.yahoo.com> Content-Language: en-CA X-CMAE-Envelope: MS4xfJlkcVzpZh7ytljciarJ/ieUx7PUE2GB8vcialVFoOxjVJD2uLsYuhMuNgwSeTJNl5hCNu81UmnJWXFtoeK16HJTqUt8PEQmxN61RaneJ+xJdF6Upf1w C3a/Kur77j3KjVo8QlthaTGlUd3pnX+6cJQpVZ5a0/gbvIk7NvE/CzNHk5lLRwVsBgo8OVv5mvfmWv8cEBrMXxWK2MErtf6I+6Y= X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, 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 AT cygwin DOT 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: , Reply-To: cygwin AT cygwin DOT com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On 2021-01-21 09:02, matthew patton via Cygwin wrote: > On Thursday, January 21, 2021, 10:49:14 AM EST, Martyn B wrote: >> On 2021-01-21 11:13, Ken Brown via Cygwin wrote: >>> There's also /etc/bash.bash_logout. The default version of that clears the screen: >>> >>> $ cat /etc/defaults/etc/bash.bash_logout >>> [...] >>> # base-files version 4.3-2 >>> >>> # /etc/bash.bash_logout: executed by bash(1) when login shell exits. >>> >>> # The latest version as installed by the Cygwin Setup program can >>> # always be found at /etc/defaults/etc/bash.bash_logout >>> >>> # Modifying /etc/bash.bash_logout directly will prevent >>> # setup from updating it. >>> >>> # System-wide bashrc file >>> >>> # when leaving the console clear the screen to increase privacy >>> if [ "$SHLVL" = 1 ]; then >>> [ -x /usr/bin/clear ] && /usr/bin/clear >>> fi >> 1) understand why this happens. - Is this the Cygwin standard behavior? > Not in the slightest. It appears to be so: $ cygcheck -f /etc/defaults/etc/bash.bash_logout base-files-4.3-2 $ ls /etc/**/*bash_logout /etc/bash.bash_logout /etc/defaults/etc/bash.bash_logout $ zgrep bash_logout /etc/**/base-files* /etc/preremove/base-files-manifest.lst:etc/bash.bash_logout /etc/setup/base-files.lst.gz:etc/defaults/etc/bash.bash_logout Whether it should be is a good question. There's no /etc/bash_logout file under Debian, etc. but /etc/skel/.bash_logout and ~/.bash_logout also have the same clear screen code. Is (or was) /etc/bash.bash_logout that did this in the bash sources or under Fedora, which is the Linux basis for some Cygwin approaches, behaviour, and conventions? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple