Describe the bug
k9s is normally cheerfully colorful. If I run k9s under GNU Screen and enter the shell of a container and then exit it with ctrl-d, when I am returned to k9s it is in what appears to be greyscale.
I can reproduce this behavior under mate-terminal as well as urxvt, in both cases inside a GNU Screen session. Outside of a GNU Screen session I cannot reproduce this issue.
To Reproduce
Steps to reproduce the behavior (assuming k3s is started vanilla, we haven't created any resources yet):
Start a GNU Screen session: screen
Start k9s, pointing it at the k3s config: sudo k9s --kubeconfig=/etc/rancher/k3s/k3s.yaml
Hit "Enter" on the node k3s
Hit "Enter" on any pod (apparently)
Hit "s" to request a shell for any container in the pod
Expected behavior
When the shell exits - whether because the container's shell exited immediately or you hit ctrl-d to exit - we land again in k9s and it is as cheerfully colorful as ever
Actual behavior
When the shell exits - whether because the container's shell exited immediately or you hit ctrl-d to exit - we land again in k9s but it is an alternate universe where k9s suffers from depression and has forgotten to present its beautiful colors to the world. In this nightmare dimension, k9s knows only greyscale. We are in a parallel universe where k9s is a goth. All hope is lost.
Screenshots
Before asking for shell:
After exiting from shell:
Versions (please complete the following information):
I am running k9s with k3s inside a virtualbox guest
The virtualbox host is Debian Bullseye
The virtualbox guest is Debian Buster
Gnu Screen is from the debian repositories at version 4.06.02
Describe the bug k9s is normally cheerfully colorful. If I run k9s under GNU Screen and enter the shell of a container and then exit it with
ctrl-d
, when I am returned to k9s it is in what appears to be greyscale.I can reproduce this behavior under mate-terminal as well as urxvt, in both cases inside a GNU Screen session. Outside of a GNU Screen session I cannot reproduce this issue.
To Reproduce Steps to reproduce the behavior (assuming k3s is started vanilla, we haven't created any resources yet):
screen
sudo k9s --kubeconfig=/etc/rancher/k3s/k3s.yaml
k3s
Expected behavior When the shell exits - whether because the container's shell exited immediately or you hit ctrl-d to exit - we land again in k9s and it is as cheerfully colorful as ever
Actual behavior When the shell exits - whether because the container's shell exited immediately or you hit ctrl-d to exit - we land again in k9s but it is an alternate universe where k9s suffers from depression and has forgotten to present its beautiful colors to the world. In this nightmare dimension, k9s knows only greyscale. We are in a parallel universe where k9s is a goth. All hope is lost.
Screenshots Before asking for shell:
After exiting from shell:
Versions (please complete the following information):