Now that I am back at the house I thought maybe a little education would be in order for those who don't know and would be interested in learning. I am going to try to make the problem that I have with the ssh session a lot more clear.
A standard Linux distro install usually comes complete with a Desktop Manager (DM) a Desktop Environment (DE) a GUI and window manager and all of that runs run top of the X window system. The system boots to a graphical login which opens up to your DE. That process opens on tty7 (F7). If you Ctrl+Alt+F1 through F6 you will find yourself at text terminal login prompt where you will have to login to do anything. A not so standard install, such as building the entire system from source code, might not have the X window system, DM, DE, GUI or window manager. At boot that system will bring you to the text terminal with a command prompt where you will have to login to do anything. This will usually be tty1 (F1).
I am using PCLOS, which boots up to tty7 or F7 and I am connecting via SSH to a system that boots up to tty1 or F1. The only time I have any problem at all with doing that is when I try to launch vi or vim on the remote system running without graphics. And, Only when I do it through KDE 4's Konsole, which uses xterm. run echo $TERM in konsole it produces xterm. run the same echo $TERM at the command prompt when at tty1 through tty6 it produces linux.
If I by pass the KDE 4 Konsole and use xterm directly ssh into the remote and run vi or vim I don't have a problem at all. I also do not have a problem when in tty1 through tty6 connecting to the remote. and like wise, I don't have a problem if the remote also has a DM, DE, GUI, window manager and the X window system. As I have said several times already the only time I have a problem using vi or vim on the remote is when the remote does not have graphics ability installed and only when using the application called Konsole in KDE 4. Using the application called xterm does not have a problem. Using the application called konsole in KDE 3.5.10 does not have a problem either.
There is something screwy going on with the application called Konsole in KDE 4 when connecting via ssh and trying to run vi or vim on a non-graphical remote system. I still have not been able to determine if this is a PCLOS or a KDE wide problem.
I really hope this is clear.