I noticed the same on some systems. I wasn't yet able to pin down the
reason, but a simple 'reset' command resets the shell to sane beaviour.
It's a workaround for the time being.
On Sun, 24 Mar 2019 at 13:28, Antonis Tsolomitis <
antonis.tsolomi...@gmail.com> wrote:
>
> I tried on ArchLinux (cde
Thanks for the answers, I did not write to the previous answers I
received
because I can no longer login CDE, and I do not know what changed,
since
I did not used CDE after my last email about the terminal problem.
It complains that can not con
