If you set Kermit, for example, to a VT100 terminal and then get your environmental TERM variable set to vt100, you should be able to use vi or emacs. I haven't taken the time to learn emacs yet, but I think it works just fine if your terminal types agree. Also, you can set environment variables for vi such as declare -x EXINIT="set wrapmargin=15" in your .bash_profile and vi will automatically wrap at word breaks much like a word processor only not nearly as smart, but still nice. If you see a message from a UNIX system that goes something like "Don't know what kind of terminal type you are using. Using open mode." You can be sure that either something isn't set right or at all. Somehow, the shell isn't understanding what kind of terminal you want to use so vi is going in to the dummest teletype mode it can to try to make it work for you. Martin McCormick WB5AGZ Stillwater, OK OSU Center for Computing and Information Services Data Communications Group brent harding writes: >I thought the only way to edit files effectiely through speech was directly >at the keyboard, but maybe my old shell account didn't support the terminal >type I was using, it often set things to dumb terminal type.
