Re: [expert] vim leaves "c" behind
On Mar 09, Jeff Stewart wrote: > 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') I would do it a tiny bit different... I would put this script into $HOME/bin/vi (and make one for view), change the $1 to $*, and make sure that $HOME/bin is in the PATH before the system-wide bin directories -Michael -- No, my friend, the way to have good and safe government, is not to trust it all to one, but to divide it among the many, distributing to every one exactly the functions he is competent to. It is by dividing and subdividing these republics from the national one down through all its subordinations, until it ends in the administration of every man's farm by himself; by placing under every one what his own eye may superintend, that all will be done for the best. -- Thomas Jefferson, to Joseph Cabell, 1816
Re: [expert] vim leaves "c" behind
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 > >
Re: [expert] vim leaves "c" behind
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 -- == "Definitions involving chicken heads no longer apply." -Jon katz ==
[expert] vim leaves "c" behind
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
