I'm thinking that this may be small problem with the KDE konsole. (At
least that's where I've noticed it). A simple kludge around this is to
set TERM=linux prior to running vi. I just aliased vi & view to my little
3 line script like such:
export TERM=linux
/bin/vi $1
export TERM=xterm
I put this is in ~/bin and called it myvi. Then I just put added the
alias to .bashrc. (alias vi='$HOME/bin/myvi')
--
Jeff
On Wed, 8 Mar 2000, Sheldon Lee Wen wrote:
> Yup, I noticed too. I took out the stupid word wrap thing now I
> get a c. Go fig.
>
> "Sang Y. Yum" wrote:
> >
> > Has anyone noticed this? After editing a file with
> > vim, I get a "c", like this:
> >
> > [sang@pikatsu sang]$ vi test.txt
> > c[sang@pikatsu sang]$ vi test2.txt
> > c[sang@pikatsu sang]$
> >
> > What gives?
> >
> > Sang
> >
> > =====
> > Sang Y. Yum http://www.yumnet.dyndns.org/~sang
> > San Diego, CA mailto:[EMAIL PROTECTED]
> > __________________________________________________
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
>
>
