public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Terminal output disappearing after SSH into cygwin
Date: Fri, 22 Jan 2021 17:16:36 +0100	[thread overview]
Message-ID: <d564b1a9-8428-0c78-296a-65fe927385bc@towo.net> (raw)
In-Reply-To: <279a917b-7053-3ce8-c071-9c2a959341fa@gmail.com>

[somehow my previous response did not go to the list]

Am 22.01.2021 um 12:10 schrieb Marco Atzeri via Cygwin:
> On 22.01.2021 09:16, Brian Inglis wrote:
>> 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:
>>>>>
>
>>
>> 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?
>>
>
>
> $ cygcheck -l base-files |grep logout
> /etc/defaults/etc/bash.bash_logout
>
> the defaults is copied as
>    /etc/bash.bash_logout
> only if it was not modified.
>
> The file is there by at least 2016, so not a new implementation
The clear is conditional. Maybe the value of $SHLVL after ssh login has 
changed somehow?


  parent reply	other threads:[~2021-01-22 16: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
2021-01-22 11:10         ` Marco Atzeri
2021-01-22 13:18           ` (SOLVED) " Martyn B
2021-01-22 16:16           ` Thomas Wolff [this message]
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=d564b1a9-8428-0c78-296a-65fe927385bc@towo.net \
    --to=towo@towo.net \
    --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).