From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Terminal output disappearing after SSH into cygwin
Date: Fri, 22 Jan 2021 01:16:17 -0700 [thread overview]
Message-ID: <9a0ce80d-fcdb-9f07-788c-c157a2de8535@SystematicSw.ab.ca> (raw)
In-Reply-To: <190171158.2668557.1611244936009@mail.yahoo.com>
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.]
next prev parent reply other threads:[~2021-01-22 8:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:08 Martyn B
2021-01-21 13:13 ` Takashi Yano
2021-01-21 13:29 ` Takashi Yano
2021-01-21 14:45 ` Martyn B
2021-01-21 17:28 ` Takashi Yano
2021-01-21 18:13 ` Ken Brown
2021-01-21 18:30 ` Takashi Yano
2021-01-21 19:06 ` matthew patton
2021-01-21 19:32 ` Ken Brown
2021-01-21 15:13 ` Marco Atzeri
2021-01-21 15:49 ` Martyn B
2021-01-21 16:02 ` matthew patton
2021-01-22 8:16 ` Brian Inglis [this message]
2021-01-22 11:10 ` Marco Atzeri
2021-01-22 13:18 ` (SOLVED) " Martyn B
2021-01-22 16:16 ` Thomas Wolff
2021-01-23 13:22 ` Martyn B
2021-01-23 14:50 ` Thomas Wolff
2021-01-22 15:27 ` Ken Brown
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=9a0ce80d-fcdb-9f07-788c-c157a2de8535@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).