We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please verify these before submitting an issue.
Termshark TUI is wierd on archlinux.
It looks wierd and different from README.md screenshots.
Just like what it likes like in README.md
Bash shell.
I've tried termshark on archlinux in WSL2, a real archlinux and ubuntu.
I use them through ssh.
In archlinux, TUI just broken like screenshots above.
BUT when I use ssh to connect to an ubuntu, and run termshark on it, it looks fine, even thought ssh runs on archlinux.
So I think there must be something wrong with termshark on archlinux, and it's not the terminal's problem, because termshark runs well throught ssh.
According to #126, I've tried export TERM=xterm-256color, but not thing changed.
export TERM=xterm-256color
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Prerequisites
Please verify these before submitting an issue.
Problem
Termshark TUI is wierd on archlinux.
Current Behavior
It looks wierd and different from README.md screenshots.
Expected Behavior
Just like what it likes like in README.md
Screenshots as applicable
Steps to Reproduce
Context
Bash shell.
I've tried termshark on archlinux in WSL2, a real archlinux and ubuntu.
I use them through ssh.
In archlinux, TUI just broken like screenshots above.
BUT when I use ssh to connect to an ubuntu, and run termshark on it, it looks fine, even thought ssh runs on archlinux.
So I think there must be something wrong with termshark on archlinux, and it's not the terminal's problem, because termshark runs well throught ssh.
According to #126, I've tried
export TERM=xterm-256color
, but not thing changed.The text was updated successfully, but these errors were encountered: