You are not logged in.

#1 2009-04-19 23:24:53

ash
Member
Registered: 2008-12-17
Posts: 134

vim is screwed

in vim when i am in insert mode (i) i hit backspace

instead of deleting (as it allways did) it adds blue '^?' to the text

whats up with it ?

Offline

#2 2009-04-19 23:50:12

rson451
Member
From: Annapolis, MD USA
Registered: 2007-04-15
Posts: 1,233
Website

Re: vim is screwed

Try adding something like this to your .vimrc and see if it helps:

" Make backspace act normal
set backspace=indent,eol,start

I have a feeling this won't help, but it's worth a try.


archlinux - please read this and this — twice — then ask questions.
--
http://rsontech.net | http://github.com/rson

Offline

#3 2009-04-19 23:53:02

cactus
Taco Eater
From: t͈̫̹ͨa͖͕͎̱͈ͨ͆ć̥̖̝o̫̫̼s͈̭̱̞͍̃!̰
Registered: 2004-05-25
Posts: 4,622
Website

Re: vim is screwed

Sounds like a termcap/terminfo issue, or possibly some other terminal setting.

Similar things happened to me a while ago with some boxes at work, and using screen:
http://cactuswax.net/articles/2008-07-2 … jinks.html

Last edited by cactus (2009-04-19 23:53:52)


"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍

Offline

#4 2009-04-20 02:11:11

xstaticxgpx
Member
Registered: 2008-10-22
Posts: 48

Re: vim is screwed

I also have this issue but only in tty's... my .vimrc's have 'set backspace=indent,eol,start'

Offline

#5 2009-04-22 02:58:40

ssjlegendx
Member
Registered: 2008-01-01
Posts: 94
Website

Re: vim is screwed

cactus wrote:

Sounds like a termcap/terminfo issue, or possibly some other terminal setting.

I essentially agree with cactus.

It's definitely not an issue with Vim itself (or your Vim configuration). Your terminal is misinterpreting your input.

I want to say that the issue could involve /etc/inputrc, but I could be wrong. I think that there are ways to configure input interpretation per-terminal-app.

The shell you're using could also be playing a part (though I'm not sure if that could affect the behavior inside Vim). If I remember correctly, using bash instead of the given default ksh solved the issue (at least partially) for me on one machine.


#!/vim/rocks

Offline

Board footer

Powered by FluxBB